CASMPET-7207: Add new permissions for the tapms operator role in vault.

[ndavidson-hpe]

Summary and Scope

This only adds more permissions to the tapms operator to allow it to create policy and roles for tenant specific transit engines. The only change in how the auth policy works is allowing tapms-operator to create and delete specific policy only for tenant specific endpoints. Vault has no more openings only allowing new policy to be made.

Issues and Related PRs

• Works on CASMPET-7207

Testing

Tested on:

• Beau

Test description:

The test was to put the new policy up and see if the tapms-operator has correct permissions.

• Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?y
• Were continuous integration tests run? If not, why?y
• Was upgrade tested? If not, why?y
• Was downgrade tested? If not, why?y
• Were new tests (or test issues/Jiras) created for this change?y

Risks and Mitigations

Low risk as it only opens endpoints that the tapms-operator can access.

Pull Request Checklist

• Version number(s) incremented, if applicable
• Copyrights updated
• License file intact
• Target branch correct
• CHANGELOG.md updated
• Testing is appropriate and complete, if applicable
• HPC Product Announcement prepared, if applicable

[ethanholen-hpe]

👍🏻