Need to add/update a contributing document with process for releasing OSCAL-Pages

[Compton-US]

Need to cover:

1. Content tied to a release of OSCAL (i.e., Content that must be coordinated with a future version release.)
2. Content that is independent of a release (i.e., Events, general content adjustments, etc)

The plan:

• Feature branch with release/version independent content merges to main directly for immediate release.
• All future content for a coordinated release goes to develop.
  • Prior to OSCAL release, develop is rebased on main
  • Develop is merged to main.

Maybe we have labels for immediate release, hold for event, etc? These could be applied to PRs/Issues? This would support release of content for events or specific dates, and not just OSCAL releases.

[Compton-US]

Per discussion with @aj-stein-nist and @nikitawootten-nist in stand up today. (Although I added the label thought just now)

[Compton-US]

Added PR #37 to address this issue and the v1.1 Release Draft