Upgrade puppet to 7.34.0

[realsdx]

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?

Change Log

• Change
• Change
• Change

Does this affect the toolchain?

NO

Associated issues

• ADO Work Item

Links to CVEs

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

Test Methodology

• Pipeline build :
  [Failed]: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=691878&view=results
  [Build Passed]: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=693189&view=results - Some Package Tests are still failing
  [After Rebase]: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=703166&view=results
  [Last Change]: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=707344&view=results
  Note: Ptests for dependencies facter and hiera are failing. Locally installed the built rpm to test the installation.
  
  

[mbykhovtsev-ms]

Extended packages should not target FastTrack, instead target 3.0-dev and potentially promote the package to core.