Release 1213.0.0

[Cal-L]

Explanation

Minor release for @metamask/remote-feature-flag-controller -> 6.0.0 -> 6.1.0
Also bumps direct dependencies

References

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
Dependency and changelog-only release with a backward-compatible optional API parameter; no breaking changes in this diff.

Overview
Monorepo release 1213.0.0 ships @metamask/remote-feature-flag-controller 6.1.0 and aligns dependents on ^6.1.0.

The release documents 6.1.0 as adding an optional force argument on updateRemoteFeatureFlags so callers can refresh remote flags even when the cache has not expired (default false; still no fetch when the controller is disabled). This PR itself is mostly version bumps, changelog entries, and yarn.lock updates across packages that depend on the controller (e.g. assets, network, transaction, wallet, bridge, config-registry).

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0a4ed26. Configure here.}

[Mrtenz]

@metamaskbot update-changelogs

[metamask-ci]

✅ Changelogs updated and pushed.