SSHOTCP-7294 Migrate the Slingshot 2.2.0 HPCM/Baremetal FM RBAC policy into CSM

[sehan-snyk]

Summary and Scope

Summarize what has changed. Explain why this PR is necessary. What is impacted? Is this a new feature, critical bug fix, etc?

The PR is about migrate the Slingshot 2.2.0 HPCM/Baremetal FM RBAC policy into CSM.

Is this change backwards incompatible, backwards compatible, or a backwards compatible bugfix?

The feature is supported from CSM 1.6 and above.

Issues and Related PRs

List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

• Resolves [issue id](issue link) : n/a
• Change will also be needed in <insert branch name here> release/csm-1.6
• Future work required by [issue id](issue link) : n/a
• Documentation changes required in [issue id](issue link) : n/a
• Merge with/before/after <insert PR URL here>

Testing

List the environments in which these changes were tested.

Tested on:

• <development system> : no
• Local development environment : New unit test cases were added and pass 100%
• Virtual Shasta

Test description:

How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?

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

Risks and Mitigations

Are there known issues with these changes? Any other special considerations?

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