Should oids.json automatically update based on Markdown table changes?

[johngray-dev]

JSON Portable OID format is created as follows:

• the https://github.com/IETF-Hackathon/pqc-certificates/blob/master/docs/oids.json file is automatically updated from the Main OID markdown file https://github.com/IETF-Hackathon/pqc-certificates/blob/master/docs/oid_mapping.md
• The update is triggered when https://github.com/IETF-Hackathon/pqc-certificates/blob/master/src/pqc_report_writer_common.py is run, and that file is triggered when the automation of the artifacts is run
• The result file will be inside the docker imagine created during the automation run, and it is not added back into the main repository

Ideally the oids.json file would be updated automatically. Further discussion needed. A couple possibilities discussed at our August 6th 2024 meeting:

1. The updated oids.json inside the docker could be copied out and published to the report page.
2. Could the published version be automatically committed?
3. The generation could be separated out, maybe into its own github action.