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
CODEOWNERS and review routing only; no application or library runtime behavior changes.

Overview
Adds @MetaMask/emerging-opportunities as a co-owner on packages that were previously owned only by @MetaMask/networks (or jointly with mobile/extension platform), so GitHub auto-requests review from both teams.

Ownership is updated in codeowners.ts (source of truth) and the generated .github/CODEOWNERS. config-registry-controller now lists Networks and Emerging Opportunities. Five local-chain / test-validator packages (bitcoin-regtest-up, java-tron-up, local-node-utils, solana-test-validator-up, stellar-quickstart-up) gain Emerging Opportunities alongside their existing joint owners, including matching package.json / CHANGELOG / tsconfig release rules.

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