Subset of permissions check on creation

[derek-ho]

Description

This PR adds permission checks around API token creation, and cleans up misc. items from the feature branch, including authorizing API token endpoint properly and stashing the context in order to perform the API token refresh action without explicit permission to do so. This PR is dependent on #4992 to be merged first, and this PR only contains the following changes:

https://github.com/opensearch-project/security/pull/5012/files/aa506e78eb5699d2580e28d4bb0f0060971449e1..e13c055e063ae3e5ee40386a53155e5c65893b58

Issues Resolved

[List any issues this PR will resolve]

Is this a backport? If so, please add backport PR # and/or commits #, and remove backport-failed label from the original PR.

Do these changes introduce new permission(s) to be displayed in the static dropdown on the front-end? If so, please open a draft PR in the security dashboards plugin and link the draft PR here

Testing

[Please provide details of testing done: unit testing, integration testing and manual testing]

Check List

• New functionality includes testing
• New functionality has been documented
• New Roles/Permissions have a corresponding security dashboards plugin PR
• API changes companion pull request created
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

Attention: Patch coverage is 80.37383% with 21 lines in your changes missing coverage. Please review.

Project coverage is 71.22%. Comparing base (0edba23) to head (bf31791).
Report is 33 commits behind head on feature/api-tokens.

Files with missing lines	Patch %	Lines
...arch/security/action/apitokens/ApiTokenAction.java	72.72%	19 Missing and 2 partials ⚠️

Additional details and impacted files

@@                  Coverage Diff                   @@
##           feature/api-tokens    #5012      +/-   ##
======================================================
- Coverage               71.46%   71.22%   -0.25%     
======================================================
  Files                     334      354      +20     
  Lines                   22552    23326     +774     
  Branches                 3590     3691     +101     
======================================================
+ Hits                    16117    16613     +496     
- Misses                   4642     4877     +235     
- Partials                 1793     1836      +43     

Files with missing lines	Coverage Δ
.../opensearch/security/OpenSearchSecurityPlugin.java	83.92% <100.00%> (+0.36%)	⬆️
...ecurity/action/apitokens/ApiTokenIndexHandler.java	84.78% <100.00%> (ø)
.../security/action/apitokens/ApiTokenRepository.java	96.96% <ø> (ø)
...earch/security/auditlog/impl/AbstractAuditLog.java	76.88% <ø> (+0.15%)	⬆️
...rg/opensearch/security/dlic/rest/api/Endpoint.java	100.00% <100.00%> (ø)
...dlic/rest/api/RestApiAdminPrivilegesEvaluator.java	73.07% <100.00%> (+0.52%)	⬆️
...pensearch/security/http/ApiTokenAuthenticator.java	58.97% <ø> (ø)
...g/opensearch/security/privileges/IndexPattern.java	95.65% <100.00%> (+0.04%)	⬆️
...arch/security/action/apitokens/ApiTokenAction.java	41.53% <72.72%> (ø)

... and 9 files with indirect coverage changes

[nibix]

I am a bit confused about returning WildcardMatcher.NONE here. Why do we do this?