Mechanism to Auto-Update GitHub Actions Configurations for OSCAL Projects

[aj-stein-nist]

User Story:

As an OSCAL tool developer, in order to simplify the management of NIST OSCAL repositories or my own repositories that leverage shared infrastructure based off of NIST OSCAL repositories, I want a mechanism for the GitHub Actions configurations for CI/CD to be analyzed and flagged for updates automatically to get updates in any repo where they are configured.

Goals:

This issue is extracted out of this recommendation in #1223 (comment) for a potential AC, moving it into its own story for ACs here.

Dependencies:

{Describe any previous issues or related work that must be completed to start or complete this issue.}

Acceptance Criteria

• All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
• 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.}

[aj-stein-nist]

This seems no longer relevant and now obsolete.