Update 3.0 manifests with missing deps

[dmcilvaney]

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

Running the make validate-chroot command shows several packages missing from the chroot environment. We need these packages to be correctly installed with all their dependencies available otherwise we may get unpredictable build results (especially for packages that are often implicitly required like util-linux).

A follow on PR will improve the detection logic, however this PR will just update the manifests and fix the toolchain build.

Change Log

• Add missing runtime requirements for a complete dependency closure in the worker chroot
  • Highlights are:
    • pam
    • pcre2 and associated sub-packages
    • libgpg-error-devel
    • libselinux
    • libsepol-devel
    • All the perl...
• Update the toolchain build script to include:
  • perl-WWW-Curl
  • python3-pyparsing
  • python3-six

Does this affect the toolchain?

YES/NO

Associated issues

• https://microsoft.visualstudio.com/OS/_workitems/edit/46755946

Test Methodology

• https://dev.azure.com/mariner-org/mariner/_build/results?buildId=684170&view=results https://dev.azure.com/mariner-org/mariner/_build/results?buildId=684176&view=results https://dev.azure.com/mariner-org/mariner/_build/results?buildId=684198&view=results
• Full: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=684178&view=results