oscal-cli validation rule for ssp/system-implementation/components/protocols/port-ranges/transport

[Telos-sa]

User Story:

As an OSCAL {stakeholder}, I want to pass a token styled data, and it still validate as long as the token format is met.

Goals:

Adjust the requirements and validations for transport token, to allow either TCP/tcp UDP/udp as either format would be an accepted token format

Dependencies:

Updating the SSP model reference on the Nist Site. Updating metaschema to support all token formats for each token, updating validation.

Acceptance Criteria

• [ ] All readme documentation affected by the changes in this issue have been updated.
• [ X ] A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
• [ ] The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}