chore: add emerging opportunities team

[taran-a]

Explanation

Ensure Emerging Opportunities is auto-requested on PRs that currently route only to the Networks team, so ownership and review coverage stay aligned across both teams.

References

• Related to WPN-1822

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
Process-only CODEOWNERS metadata; no application logic, security, or runtime behavior changes.

Overview
Adds @MetaMask/emerging-opportunities as a joint CODEOWNERS team on packages that were previously owned only by Networks (or jointly with mobile/extension platform teams), so GitHub will auto-request review from Emerging Opportunities on those PRs.

The source of truth update is in codeowners.ts for config-registry-controller and the joint-ownership local/test node packages (bitcoin-regtest-up, java-tron-up, local-node-utils, solana-test-validator-up, stellar-quickstart-up). .github/CODEOWNERS is regenerated to match, including package release paths (package.json, CHANGELOG.md, tsconfig.*).

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