Example SSP Reflecting Latest FedRAMP OSCAL Modeling

[brian-ruf]

Committer Notes

This PR contains an OSCAL SSP Example File that reflects revisions to the way required FedRAMP content is modeled in OSCAL.

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]

in fedramp_extensions.feature file line 13
Add your in progress SSP into the test runner so the github actions can capture validity of this SSP
src/content/rev5/examples/ssp/xml/FedRAMP-SSP-Example.OSCAL.xml

[aj-stein-gsa]

To start acting on this, are you OK with me converting this into a page on the developer wiki?

[kyhu65867]

Worth updating to 1.1.3?

[kyhu65867]

If this is important for all of our stakeholders to know (aka we are going to reject their package if they don't name their UUIDs correctly), it may be worth making a diagram to add to this file. (It could be worth it anyways just for the sake of clarity and so that different visual learners can understand this because I'm having trouble parsing it out)