Big Bang OSCAL Component

How should Bigbang roll up the OSCAL components defined by each package:

Option 1

In the release, it should build a single component as a release artifact. This is my least favorite since it wouldn't be available to someone who has the BigBang repo, as they would need something in Gitlab release pages

Option 2

There is a comparable OSCAL document in the repo that needs to be updated by BigBang Developers as updates to the repo occur. This could also be done by the release engineer as part of the release process (like Readme/changelog), absolving the developers needing to do this on tag bumps.

Option 3

A script that allows the generation of the OSCAL document as a function of a values.yaml file passed into BigBang is the most complicated and would require more engineering effort, but would let people generate their own component. This might have UX issues as people want to inherit controls in eMASS and now there are "different" big bangs that they could import from.

/cc @gabe @michaelmcleroy