Engineers must update the dist schemas when they change the schema

As of time of writing, the Secure Report Format project releases new schema versions by tagging a Git commit. It therefore follows that when an engineer updates the schema, the generated schema containing their change must also be committed to Git.

This MR adds a test to the CI Pipeline that reads schemas, regenerates them, reads them again, and verifies that they are the same. If there are any differences, the test and CI job will fail with a message explaining to the engineer steps they need to take.

This MR also updates the JSON schemas in the dist to be the latest version, so that this new test will pass. The README has been updated with the latest understanding of the workflow.