Add Leveraged Authorization Entry Constraints

[Gabeblis]

Committer Notes

Purpose

This PR aims to ensure that any leveraged authorization entries within the SSP have the required content to maintain compliance with FedRAMP standards. The constraints to validate the presence of said properties for each leveraged-authorization entry are to ensure the following:

• Exactly one authorization-type.
• Exactly one package identifier.
• Exactly one impact-level.

Changes

Constraints Added

• leveraged-authorization-has-authorization-type
  This constraint checks that there is exactly 1 authorization-type property for each leveraged-authorization entry.

• leveraged-authorization-has-impact-level
  This constraint checks that there is exactly 1 impact-level property for each leveraged-authorization entry.

• leveraged-authorization-has-system-identifier
  This constraint checks that there is exactly 1 system-identifier property for each leveraged-authorization entry.

ssp-all-VALID.xml was edited to include a leveraged-authorization section to trigger the above constraints.

Invalid test data files were created for each constraint to demonstrate the fail case.

pass and fail YAML files were added for each constraint.

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Have you added an explanation of what your changes do and why you'd like us to include them?
• If applicable, have all FedRAMP Documents Related to OSCAL Adoption affected by the changes in this issue have been updated.?
• If applicable, does this PR reference the issue it addresses and explain how it addresses the issue?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

[wandmagic]

nice work

[kyhu65867]

Write documentation if necessary but I think this looks good to go