Establish a shorter number-based naming convention for constraint IDs

[Rene2mt]

This is a ...

improvement - something could be better

This relates to ...

• the FedRAMP OSCAL baselines
• the FedRAMP SSP OSCAL Example
• the FedRAMP SAP OSCAL Example
• the FedRAMP SAR OSCAL Example
• the FedRAMP POA&M OSCAL Example
• the FedRAMP OSCAL Validations
• the Not sure

User Story

As a developer and/or user of FedRAMP OSCAL constraints, I would like a shorter, number-based naming convention for constraint IDs, so that I can more easily reference constraints and automate processes that rely on these IDs.

Goals

Each of the following will need to be completed but may be treated as separate sub-issues:

• Create an ADR evaluating options for constraint ID naming convention, including all structures that are all numeric, alphanumeric, etc.
• Once an option is selected, update all constraint IDs accordingly in the external constraint files (fedramp-external-allowed-values.xml and fedramp-external-constraints.xml), and their corresponding unit tests
• Update any constraint references in documentation (dev hub documentation site)

Dependencies

No response

Acceptance Criteria

• All FedRAMP Documents Related to OSCAL Adoption (https://github.com/GSA/fedramp-automation) affected by the changes in this issue have been updated.
• A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.

Other information

No response