feat: add EthKeyringWrapper for common Eth logic around KeyringV2 implementation

[mathieuartu]

Related to: https://consensyssoftware.atlassian.net/browse/MUL-1316

Examples

---

Note

Introduces EthKeyringWrapper with shared Ethereum submitRequest logic and updates HdKeyringV2 to extend it, adding RPC param structs, an EthKeyring alias, tests, and required deps.

• Keyring API:
  • New: eth/v2/EthKeyringWrapper abstract class with common Ethereum request routing (submitRequest) and EthKeyringMethod enum.
  • RPC: Add EthGetEncryptionPublicKeyOptionsStruct and EthGetEncryptionPublicKeyParamsStruct (address, optional options).
  • Exports: Re-export from eth/v2 and include new wrapper in eth/index.
  • Deps: Add @ethereumjs/tx and @metamask/eth-sig-util.
  • Tests: Add comprehensive unit tests for wrapper routing and errors.
• Keyring ETH HD:
  • Refactor: HdKeyringV2 now extends EthKeyringWrapper; removes duplicate routing, uses shared methods list including encryption/app-key/EIP-7702.
  • Tests: Adjust to pass address/options for eth_getEncryptionPublicKey and align with wrapper behavior.
  • Changelog: Note extension of EthKeyringWrapper.
• Keyring Utils:
  • New: Export EthKeyring type alias for legacy Keyring.
  • Changelog: Document alias addition.

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

[cursor]

Bug: Missing default value for params may cause unexpected errors

The params destructuring lacks a default value. The previous implementation in HdKeyringV2.submitRequest used const { method, params = [] } = request.request; but EthKeyringWrapper uses const { method, params } = request.request;. Since params is defined as exactOptional in KeyringRequestStruct, requests without params are valid and will result in params being undefined. This could cause confusing validation errors when assert is called on undefined instead of an empty array.