feat: add support for keyring_deleteAccounts

[ccharly]

Note

Medium Risk
Changes how accounts are removed across keyrings and snaps, including partial-failure semantics and SnapKeyring’s “local remove first” behavior, which can desync wallet state from snap state if remote deletion fails.

Overview
Adds bulk account deletion to the v2 keyring surface: deleteAccounts(accountIds) on the Keyring interface, the keyring_deleteAccounts RPC (params { ids }), and DeleteAccountsError with a per-account failures map when any deletion fails after a best-effort pass.

KeyringWrapper now treats deleteAccounts as the primitive implementation and provides a default deleteAccount that calls it with a single ID; Ethereum keyring adapters implement bulk delete with Promise.allSettled plus toAccountsFailures / toErrorMessage from keyring-utils. HD deletes in descending derivation order so only “last account” rules still apply during multi-delete.

The snap path wires KeyringClient.deleteAccounts, an RPC handler, and DeleteAccountsSnapError for structured snap failures. SnapKeyring clears the local registry first (same as single delete), calls bulk RPC for v2 snaps, and falls back to per-account RPC for v1; snap-side errors are logged, not thrown. MoneyKeyring keeps deletion unsupported via a no-op bulk method.

^{Reviewed by Cursor Bugbot for commit ff5e42b. 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 321066f. Configure here.}