Extends users/token GET endpoint to support any auth mechanism for retrieving the token

[GPortas]

What this PR does / why we need it:

Changes users/token GET endpoint to support any auth mechanism for retrieving the token.

Previously, this endpoint only accepted an API token to retrieve its information. Now, it accepts any authentication mechanism and returns the associated API token information.

Which issue(s) this PR closes:

• Closes Extend users/token endpoint for retrieving the token using any available API auth mechanism #10914

Special notes for your reviewer:

For private URL tokens, the endpoint returns Unauthorized. Before this change, it returned Not Found. I believe this behavior is correct since a private URL user is not considered an authenticated user and therefore cannot obtain an API token, but I think it's necessary to double-check this.

Suggestions on how to test this:

Visual inspection and call the API token endpoint with any available auth mechanism. We can test the endpoint using the session cookie authentication (we should enable the feature flag) by sending the associated cookie, and verify we obtain the API token if created.

curl --cookie "JSESSIONID=<cookie_value>" -X GET http://localhost:8080/api/users/token
Does this PR introduce a user interface change? If mockups are available, please link/include them here:

No

Is there a release notes update needed for this change?:

I am not sure, but I have added them

Additional documentation:

None

[coveralls]

coverage: 20.874% (-0.001%) from 20.875%
when pulling 129c80c on 10910-users-token-api-credentials
into c44ad65 on develop.

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:10910-users-token-api-credentials

ghcr.io/gdcc/configbaker:10910-users-token-api-credentials

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.

[ofahimIQSS]

Testing passed - merging PR.
Testing of 10924.docx