[main] Adding Mariner's GPG keys to RPM's database in the worker chroot.

[PawelWMS]

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/tools/cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/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

Recent update of TDNF made it display a few more yes/no questions, which caused failures for derivative builds reaching out to the PMC repository (no issues in core builds, since they relied on local packages). We're now making sure that RPM has imported Mariner's GPG keys before running any TDNF commands in the chroot.

Change Log

• Importing Mariner's GPG keys during chroot's creation.
• Making TNDF install Mariner's GPG keys automatically, if mariner-repos-shared is present.

Does this affect the toolchain?

Yes.

Test Methodology

• Local demo package and VHD build.