Add leveraged-authorization-has-valid-impact-level Constraint

[Gabeblis]

Committer Notes

Purpose

This PR adds a constraint to ensure that a digital authorization package maintains appropriate FIPS-199 impact levels for leveraged authorizations within an SSP. This update helps avoid pass-back errors by aligning with the system's security sensitivity level (e.g., low, moderate, or high).

Changes

• Added a new expect constraint to check that all leveraged authorizations define the appropriate FIPS-199 impact level (low, moderate, or high).
• Edited ssp-all-VALID.xml to have proper data to trigger the constraint and pass.
• Added an invalid test data file to trigger the constraint and demonstrate a successful fail
• Added pass and fail YAML files for the 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.? Documentation already exists
• 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]

looks good nice work

[aj-stein-gsa]

Looks very solid but would like the documentation change to match.

[aj-stein-gsa]

Very good work, I particularly enjoy how you document the scenarios in your passing and failing test cases over the last few weeks. Keep it up!

[Rene2mt]

Looks good to me.