fix: auth requests use org and user names if present

[williamhbaker]

Closes #22261

Fixes requests to /api/v2/authorizations so that the query parameters of user and/or org will be used to populate the filter with the respective ID's if user/org are present but userID/orgID are not in the query.

Giving precedence to the ID parameters if they are present over the "name" parameters seems to be consistent with how other resource endpoints work. For example, if you provide both a user and a userID, the userID will be used to filter the authorizations.

[gwossum]

Looks like it should work as described. Are there test cases that test if an invalid user or org are in the query? Couldn't tell if there were any tests cases that did that.

[williamhbaker]

Looks like it should work as described. Are there test cases that test if an invalid user or org are in the query? Couldn't tell if there were any tests cases that did that.

It goes through the tenant service, which will cause the handler to return an error (404 HTTP response) if the request user or org name doesn't exist. There aren't tests directly here for that, but the tenant service does have tests for org not found and user not found.

[gwossum]

I've seen enough. Approved.