kata-containers(-cc): Use build recipes from sources

[manuelh-dev]

Merge Checklist

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

• [x] The toolchain has been rebuilt successfully (or no changes were made to it)
• [x] The toolchain/worker package manifests are up-to-date
• [x] Any updated packages successfully build (or no packages were changed)
• [x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• [x] 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
• [x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• [x] 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)
• [x] All source files have up-to-date hashes in the *.signatures.json files
• [x] sudo make go-tidy-all and sudo make go-test-coverage pass
• [x] Documentation has been updated to match any changes to the build system
• [ ] Ready to merge

---

Summary

This commit simplifies package and UVM build by using recipes established in our sources. These recipes also make shipping separate UVM build scripts obsolete. The UVMs can from now on be built standalone using the kata-containers-(cc-)tools subpackages

Change Log

• Use build recipes from fork

Does this affect the toolchain?

NO

Associated issues

• N/A

Links to CVEs

• N/A

Test Methodology

• buddy build runs: Pipelines - Run mahuber+kata-spec-rebuild-squash-m3-pr+kata-containers+kata-containers-cc+unknown (azure.com)
• image build runs:
  • https://dev.azure.com/mariner-org/mariner/_build/results?buildId=644906&view=results
  • https://dev.azure.com/mariner-org/mariner/_build/results?buildId=644213&view=results