Flesh out the JSON output

[JonZeolla]

Looks like we need to fill out - some examples below, but look at the JSON schema (good example here):

"published": Datetime
"revisions": [Github URI]
"document_ids": CNSWPv1
"links": ["link to the white paper"]
"roles": null,
"locations": Insert website (github repo?)
"parties": null,
"responsible_parties": null,
"remarks": null

[brandtkeller]

Running the output against a json schema validator using the oscal schema for a specified version would be a good practice. Also would shine a light on some areas where the current artifact is not a valid OSCAL catalog as of yet.

Lula and the Lula-action could be used to ensure linting in pipelines with something like lula tools lint -f controls-catalog.json as a quality gate. Lula will run a schema validation on all version >= 1.0.4