Release/1104.0.0

[hmalik88]

Explanation

Releasing the following:

account-tree-controller
assets-controllers
multichain-account-service
snap-account-service

References

N/A

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
No new runtime code in this PR, but the published majors/minors carry breaking Snap account and multichain alignment APIs that client apps must adopt when they bump these versions.

Overview
This PR cuts release 1104.0.0 by bumping package versions, finalizing changelogs, and refreshing yarn.lock—there is no application source change in the diff.

It publishes @metamask/snap-account-service@2.0.0, @metamask/multichain-account-service@12.0.0, @metamask/account-tree-controller@7.5.4, and @metamask/assets-controllers@109.3.1, and threads those versions through dependents (assets-controller, bridge-controller, earn-controller, perps-controller, transaction-pay-controller, etc.).

The breaking items called out in the released notes (already merged elsewhere) include capability-based v1/v2 Snap keyring routing, new SnapAccountService messenger actions, removal of createAccounts.batched config, and stricter RestrictedSnapKeyring v1 vs v2 usage—consumers must align messenger permissions and Snap integration when upgrading.

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

[mm-token-exchange-service]

✅ Changelogs updated and pushed.

[mcmire]

LGTM.