chore: Add approvedGitRepositories to Yarn config

[Mrtenz]

Explanation

Yarn recently added an approvedGitRepositories setting which is an allowlist for allowed Git repositories that can be installed as dependencies. Git repositories have some security risks, and we don't typically use them, so we can set it to an empty array to disallow Git repositories.

References

MetaMask/metamask-module-template#310.

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Low Risk
Low risk: config-only changes that tighten dependency policy and bump the Yarn toolchain; main impact is potential install/CI breakage if any Git-based deps were relied on implicitly.

Overview
Hardens Yarn dependency sourcing by adding approvedGitRepositories: [] to .yarnrc.yml, explicitly disallowing Git-based dependencies.

Bumps the required Yarn version from 4.10.3 to 4.14.1 (root packageManager and matching yarn constraints check), and updates yarn.lock metadata accordingly.

^{Reviewed by Cursor Bugbot for commit f0bd7f1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mcmire]

Makes sense!