Oscal schema updates support

[brandtkeller]

Attempted to generate types for 1.1.1 release of OSCAL component definition. It resulted in a lot of hard-coded assumptions breaking.

Introducing the use of jsonschema-go has hopefully made the codebase more robust and I successfully tested generation of Component Definitions from 1.0.4 -> 1.1.1

Lot's of cleanup and improvement to do. Goal here is functional code that works for all releases of component definition 1.0.4 -> 1.1.1.

This opens the doors to conversations like if there would be value/requirements for OSCAL tooling to be able to be functional for current and historical schemas of OSCAL. There may be additional logic that we can add here and expose to make de-duplication possible while referencing multiple specific versions. Creating additional issues for TODO items in the backlog.

[brandtkeller]

Marking ready for review and will be opening issues to capture work around schema validation that needs to occur with anyOf/allOf items and existence of enums.

[Alvin-zzz]

Looks good, thanks for the hard work!