Split centralized manifest.json into per-spec manifest.json files

[ahelwer]

In furtherance of #171. These changes:

• Initially modify generate_manifest.py to split the existing manifest into per-directory manifests
• Append the output of running the generate_manifest.py script, which is a large number of small manifests
• Change the manifest-schema.json to validate the split manifests
• Change all the CI validation scripts to use split manifests
• Change the CI workflow itself to use the updated script arguments
• Deletes the central manifest.json file
• Update the repository documentation to reflect the new split nature of the manifest

Now that we have per-spec manifests, we can incrementally devolve the various components of the manifests into either the README table or the specs themselves. Ideally we will reach a world where no manifests exist at all, but some features like recording the model state count will make that difficult. Putting those details as comments in the model is one possibility.

[lemmy]

This is factually incorrect. These specifications may not be covered by the CI in this repository, but they could be managed by their own dedicated CI pipelines. For example, the BlockingQueue specs have their own CI.

[ahelwer]

If the BlockingQueue repository is moved or deleted then it will no longer be available, as stated. Although this itself will probably be detected in the next CI run, when git tries to clone a submodule that no longer exists.

[lemmy]

Again, why not have a single table that has an additional column that indicates if a spec has CI?

[ahelwer]

We can certainly look at doing that in the future, but that's beyond the scope of this PR.

[lemmy]

I don't know enough about the python tooling to review it. The markdown files and the CI.yml look ready to merge (modulo my comments below).