Add Prism configuration for select baremetal, qemu-guest, marketplace-gen1, and marketplace-gen2 images

[vinceaperri]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Adds Prism YAML configuration for the baremetal, qemu-guest, marketplace-gen1, and marketplace-gen2 images, for both x86_64 and aarch64 (where supported).

Change Log

• Translated existing baremetal x86_64 JSON config to new Prism YAML config
• Added new baremetal aarch64 Prism YAML config (size is the only change from the x86_64 config)
• Translated existing qemu-guest x86_64 JSON config to new Prism YAML config
• Added new qemu-guest aarch64 Prism YAML config (size again is the only change from the x86_64 config)
• Translated existing marketplace-gen1 x86_64 JSON config to new Prism YAML config
• Translated existing marketplace-gen2 x86_64 and aarch64 JSON config to new Prism YAML config
• Translated all package lists used by the image configs above to Prism YAML configs

Does this affect the toolchain?

NO

[reubeno]

How are we planning to keep these from diverging from the current JSON-based configurations? Can we instead auto-generate these? Or vice versa? Or add checks to ensure they're consistent?

Is there a long-term plan for deprecating the JSON configs?

[cwize1]

Use size instead of start and end. Same comment elsewhere.

[cwize1]

base-image-packages and core-packages-image are kind of confusing names. I think you are copying the existing names from the json files. But I wonder if we should take the opportunity to improve the names somewhat.

[cwize1]

Any reason you are duplicating packages that are in the seed image?