feat: use @metamask/native utils

[Nodonisko]

This PR adds support for using faster native functions in mobile app environments for cryptographic functions. It's relying on RN Metro bundler internal mechanism where it automatically prefer files with .native.ts suffix.

---

Note

Introduces React Native native cryptography implementations and a unified getPublicKeyForCurve API, refactoring key/address derivation to use it and updating exports, tests, coverage, and peer deps.

• Cryptography (Core/API):
  • Add src/cryptography/cryptography.native.ts with native hmacSha512, keccak256, pbkdf2Sha512, sha256, ripemd160, and getPublicKeyForCurve using @metamask/native-utils/react-native-quick-crypto.
  • Introduce getPublicKeyForCurve in src/cryptography/cryptography.ts and export via src/cryptography/index.ts and root src/index.ts.
  • Add src/cryptography/cryptography.types.ts with typed override surface.
• Derivation Refactors:
  • Replace curve-specific public key derivations with getPublicKeyForCurve in SLIP10Node, derivers/bip39.ts, derivers/cip3.ts, and derivers/bip32.ts.
  • Update publicKeyToEthAddress signature to accept optional CryptographicFunctions; propagate in SLIP10Node.address.
  • Update getFingerprint to accept optional CryptographicFunctions and wire in SLIP10Node.fingerprint.
• Exports/Tests:
  • Export new cryptography functions from package root and add tests for hashing functions and getPublicKeyForCurve; update index export coverage tests.
• Tooling/Config:
  • Jest: exclude *.native.ts from coverage collection.
  • Add dev/peer deps: @metamask/native-utils, react-native-quick-crypto with optional peer metadata.

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