Profile fix issue 1102

[Rene2mt]

Committer Notes

This PR fixes the reported issue #1102 by:

• Adding the FedRAMP namespace to any parts added in the FedRAMP (High, Moderate, Low, and LI-SaaS) profiles.
  • This eliminates errors in resolved profiles due to unexpected parts (e.g., `..) in the resolved profile catalogs
  • This makes it easier for consumers of the FedRAMP resolved profile catalogs to identify FedRAMP specific alterations (e.g., Additional FedRAMP requirements and guidance)
• Fixed duplicate part IDs in High and Moderate profiles.
• Updated the last-updated, version, and oscal-version in the metadata of the FedRAMP (High, Moderate, Low, and LI-SaaS) profiles.

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.

[Gabeblis]

LGTM

[Gabeblis]

I know this was brought up in conversation before, but per the issue, "Fixes only need to be made to the XML profiles, and will cascade to the all formats (XML, JSON, and YAML) during CI profile resolution and conversion.", are we sure that these changes will cascade to all formats or should we manually apply these changes?

[aj-stein-gsa]

I know this was brought up in conversation before, but per the issue, "Fixes only need to be made to the XML profiles, and will cascade to the all formats (XML, JSON, and YAML) during CI profile resolution and conversion.", are we sure that these changes will cascade to all formats or should we manually apply these changes?

We are going to need to release for this to happen automatically with CI (as that only happens on master branch based on current GitHub Actions configuration) or manually push it into develop. From recollection, you do it enough the latter way manually with a developer committing outside of CD you have some fun, gnarly merge conflicts in some cases. FYI/FYE

[aj-stein-gsa]

Minor feedback, but good to go otherwise. I approve.