Inconsistencies in Admin API based user listing

[poikilotherm]

What steps does it take to reproduce the issue?
Look at the outputs of /api/admin/authenticatedUsers and /api/admin/list-users

When does this issue occur?
When using the API to retrieve all users

Which page(s) does it occurs on?
API

What happens?

1. I must supply a Superuser Admin Token to both endpoints in addition to my unblock-key. This doesn't make sense and should be mitigated (instead of access policy unblock-key or localhost allow a policy to use tokens, OIDC or API style).
2. The /list-users endpoint is inconsistent with it's naming. Why isn't this paginated, searchable output enabled under /authenticatedUsers?
3. The /list-users endpoint doesn't use the JsonPrinter.json(AuthenticatedUser) to include the persistentUserId in the JSON output, while the /authenticatedUsers endpoints do. Instead, it uses the AuthenticatedUser.toJson() converter, which is solely used for this purpose, nowhere else except a test of the AuthenticatedUserclass.
4. Why is the /authenticatedUsers endpoint deprecated, when there are a lot more endpoints using this path?
5. Why is the API endpoint to change a user identifier under /api/users instead of /api/admin/authenticatedUsers when it does require a superuser token anyway?
6. Why aren't there simple CRUD like endpoints for /api/admin/authenticatedUsers/{id}/{attribute}?

To whom does it occur (all users, curators, superusers)?
Superusers, Admins

What did you expect to happen?
See list above.

Which version of Dataverse are you using?
4.20 and develop.

Any related open or closed issues to this bug report?
None that I could find.

[pdurbin]

Per discussion in Slack, /api/admin/list-users was added in this PR:

• 3614 user list #3877

As I said there, at some point the SPA will probably need a new non-blocked (not under /api/admin) endpoint for the users part of the superuser dashboard. Perhaps that would be a good time to clean things up. 😅