port perl modules from extended to core

[neha170]

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

ports some perl packages from extended into core

Change Log

• ports some perl modules from extended into core:
• perl-B-Hooks-OP-Check
• perl-ExtUtils-Depends
• perl-multidimensional
• part of the bigger effort

Does this affect the toolchain?

NO

Associated issues

• 53283603

Test Methodology

• Pipeline build successful, fails on installation: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=626320&view=results

[rikenm1]

Looks good but do we not have to update them when migrating from extended to the core.?

[neha170]

Looks good but do we not have to update them when migrating from extended to the core.?

Yep, that will be taken up in a separate task. This is required to fix a P0 for 3.0 release.

[rikenm1]

LGTM