Decompose OSCAL and Validations

[brandtkeller]

Is your feature request related to a problem? Please describe.

An emerging theory around the development of validations is how to best capture continual development work.

One workflow is to decompose a composed OSCAL file to allow for quick feedback loops of updating a given validation and performing /developing tests.

Describe the solution you'd like

• Given a composed component-definition
• When tools decompose is executed
• Then the file is deconstructed to place validations in a local directory for further development

Describe alternatives you've considered

Manual processes but much the same

Additional context

When decomposing - we may not want to put UUID in the validation metadata. If that UUID is supposed to change when modified then it may be something we automate. Review OSCAL identifier use

When decomposing - we should look into removing extra whitespace to ensure readable formatting.