Goal:

• Deprecate the https://github.com/osbuild/manifest-db/ repository.
• Generate image-info reports for testing manifests as part of https://github.com/osbuild/images/ CI.
• Move image-info tool to https://github.com/osbuild/osbuild/ under tools/.
• Switch manifest tests in https://github.com/osbuild/osbuild/ to use manifests and image-info reports generated as part of https://github.com/osbuild/images/ CI.

Acceptance Criteria:

• https://github.com/osbuild/manifest-db/ is archived and not used any more by any other repository / project.
• image-info tool is part of https://github.com/osbuild/osbuild/ under tools/.
• image-info reports are generated as part of https://github.com/osbuild/images/ CI.
• manifest tests in https://github.com/osbuild/osbuild/ CI use manifests and image-info reports generated in https://github.com/osbuild/images/ CI.

Open questions:

• akoutsou@redhat.com has some additional ideas: 

  Generally: yes, let's drop it.
  More specifically: maybe let's replace it with something else.  I think the functionality it serves now should be in images (image info checking and stuff like that), as recommended here.  But I'd love if we had something that's closer to what the name of the repo implies: A database of manifests (image definitions) that we can use for reference.

  First, it can just be a bunch of manifests and image info, generated from images CI (where we already do generate everything) and we can look at to answer questions like "what's the size of boot partition in all qcow2 images?".  For us, this can be a quick `grep` through image info which would be nice to have in a central place (and doesn't require reading code and tracing value replacements).

  After that, it'd also be nice if we could make it a bit more accessible.  Maybe simply a page that renders all the image info json files in a nice way that people can filter through (nothing fancy, just a quick table view of the most important things people might want to see).