[#12048] Migrate tests for GetUsageStatisticsActionTest

[InfinityTwo]

Part of #12048

Outline of Solution
Added the unit tests for GetUsageStatisticsActionTest for PostgreSQL.

[jasonqiu212]

lgtm! good work

[jasonqiu212]

Was thinking if we can explore abstracting the access control tests in sqlui/webapi/BaseActionTest.java, like in the old tests. Currently, I feel like there's a lot of repeated code for testing access control

[InfinityTwo]

Was thinking if we can explore abstracting the access control tests in sqlui/webapi/BaseActionTest.java, like in the old tests. Currently, I feel like there's a lot of repeated code for testing access control

Hmm, great idea, I was thinking of it as well instead of copy pasting it for each new migrated test. I think the next time I work on it, I'll add the abstraction and do a refactor of the PRs.

Do you think we should make it similar to the previous method names such as verifyOnlyAdminsCanAccess() or should we have one method for it all, and pass in 6? boolean parameters for each user type?

[jasonqiu212]

@InfinityTwo That would be great! thank you!!

Let's follow the previous method names (i.e., having 1 method for each role). I think this follows open-closed principle more (please correct me if i'm wrong..), since if we have additional user types, we just simply add a new method, and the old methods do not need to be modified.

If we have 1 method for all roles, and pass in boolean parameters for each role, adding a new user type means we need to change all of the method calls' arguments to add in the new boolean for the new role.

[domoberzin]

LGTM!