[3.0] Upgrade cert-manager to v1.15.3

[Camelron]

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
• [x] 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 (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/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
• [x] Ready to merge

---

Summary

What does the PR accomplish, why was it needed? Package upgrade for azl3; move to v1.15.3.

Introduces nested-vendoring.sh which handles the vendoring for nested go modules in a single source tar.

Addresses CVEs CVE-2023-45142, CVE-2023-6337.

Change Log

• Upgrade cert-manager to v1.15.3

Does this affect the toolchain?

NO

Test Methodology

• local build

[romoh]

Upstream is now at 1.14.2

[troy0820]

Are we still going to v1.15.3? Upstream has a release that is v1.16.2. I was trying to move this to v1.16.1 if we could but didn't want to get in the way of this artifact. @romoh @Camelron