chore!: bump accounts deps

[ccharly]

Explanation

Bumping accounts deps and re-adapt usage of InternalAccount.metadata.snap.{enabled,name}.

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
Introduces a breaking change to Snap account metadata and changes how Snap accounts are grouped/enabled by delegating to SnapController:getSnap, which can affect wallet categorization and downstream consumers relying on the old fields/events.

Overview
Snap account classification now consults SnapController rather than InternalAccount.metadata.snap.enabled. SnapRule calls SnapController:getSnap to confirm a Snap exists and is enabled; Snap accounts referencing missing Snaps are no longer treated as Snap wallets and fall back to keyring-based grouping, with tests updated accordingly.

Accounts-related packages are updated for the new Snap metadata shape. The AccountsController drops its SnapController:stateChange subscription and the logic/tests that mutated metadata.snap.enabled, and multiple packages bump @metamask/keyring-internal-api to ^11.0.0 (plus @metamask/eth-snap-keyring to ^22.0.0 where used); changelogs document the breaking removal of InternalAccount.metadata.snap.{enabled,name}.

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​eth-snap-keyring@​21.0.1 ⏵ 22.0.0			-1	-1
	@​metamask/​keyring-internal-api@​10.1.1 ⏵ 11.0.0

View full report

[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 c47a59d. Configure here.}

[cursor]

Missing blocked check in new #isSnapAccount method

Medium Severity

The new #isSnapAccount only checks snap.enabled but omits the !snap.blocked check. The old code in AccountsController.#handleOnSnapStateChange computed enabled as snap.enabled && !snap.blocked before storing it in account.metadata.snap.enabled, which was then checked by the old isSnapAccount. The refactored version lost the blocked guard, so a snap that is enabled but blocked will now be treated as a valid snap account instead of falling back to the keyring rule.

 

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