fix: fix keyring_createAccount idempotency

[ccharly]

The notify:accountCreated event was fired even for existing accounts, which would cause errors in the SnapKeyring handling (if the account has not been created already):

• https://github.com/MetaMask/accounts/blob/v79.0.0/packages/keyring-snap-bridge/src/SnapKeyring.ts#L342-L354

Similarly to the Solana Snap, if the account already exists, we just return the KeyringAccount object and that's it:

• https://github.com/MetaMask/snap-solana-wallet/blob/main/packages/snap/src/core/handlers/onKeyringRequest/Keyring.ts#L229-L244

---

Note

Stop emitting accountCreated when the account already exists; bump Snap version to 1.6.0.

• Core (snap):
  • AccountUseCases.create: Return existing account without emitting accountCreated to ensure idempotency.
• Manifest:
  • Bump packages/snap/snap.manifest.json version to 1.6.0 and update source.shasum.

^{Written by Cursor Bugbot for commit d57dc39. This will update automatically on new commits. Configure here.}

[ccharly]

Looks like the release workflow does not automatically update this?

[ccharly]

We still have an emitAccountCreatedEvent below, when the account got inserted for the first time.