Release 1314.0.0

[mathieuartu]

Explanation

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

Medium Risk
Medium risk from rolling out profile-sync 34.0.0’s breaking MFA/session constant removal and crypto/auth behavior changes across many consumers, even though this PR only bumps versions and lockfile entries.

Overview
This PR cuts Release 1314.0.0 by bumping the root monorepo version and publishing new package versions across the workspace—mostly dependency alignment and changelog updates, with yarn.lock refreshed to match.

The driver is @metamask/profile-sync-controller@34.0.0, which many packages now depend on (^34.0.0). That release (already documented in its changelog) changes MFA enrollment to open a server-scoped verification session, swaps client AES for @metamask/cryptography, and removes VERIFICATION_SESSION_TTL_MS as a breaking change. Downstream packages (account-tree-controller, assets-controllers, core-backend, bridge/claims/kyc/shield/subscription/wallet, etc.) get patch or minor version bumps that record those dependency updates.

A few other packages ship their own pending changelog entries in the same train (e.g. social-controllers@3.6.0, smart-transactions-controller@27.1.0, ramps-controller@26.2.0), but the diff here is almost entirely version, package.json, and CHANGELOG.md—no new runtime code in this PR.

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

[mathieuartu]

@metamaskbot update-changelogs

[cryptodev-2s]

@metamaskbot update-changelogs

@mathieuartu token-exchange service is down so do bot will likely fail run locally.

yarn changelog:validate --checkDeps --fix --currentPr "10662"