[3.0] Introduce debug and metapackage and reduce size of non-debug metapackage

[Camelron]

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

What does the PR accomplish, why was it needed?
Introduce kata-packages-uvm-debug metapackage

Change Log

• Introduce kata-packages-uvm-debug metapackage
• Move curl, cpio, gzip, iputils, lvm2, tar, procps-ng to debug metapackage
• Remove bash, grep, readline, util-linux from all metapackages (implicit deps of existing requirements)
• Add findutils to debug metapackage

Does this affect the toolchain?

YES/NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Tested via kata image build, kata conformance tests pass https://dev.azure.com/mariner-org/mariner/_build/results?buildId=760112&view=results
• Deployed dev image, inspected the new set of images. Noted a net saving of ~8Mb in image size for the release UVM image
  

[reubeno]

While we're in here making changes, is it worthwhile documenting (via inline comments) why these specific packages are still required (at least for the dependencies that we know about)? Even if it's incomplete, it may help devs who come along later understand why, say, chrony is required.

[Copilot]

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)

• SPECS/kata-packages-uvm/kata-packages-uvm.spec: Language not supported