feat(me): add multisigTypeVersion routing for EdDSA MPCv2 key gen

[Marzooqa]

What

• Add multisigTypeVersion as an optional request parameter to the generate-wallet route codec in src/masterBitgoExpress/routers/generateWalletRoute.ts (MPCv1 or MPCv2, absent = coin default = MPCv1 for backward compatibility)
• Branch the keyGenCallbacks routing in src/masterBitgoExpress/handlers/handleGenerateWallet.ts:
  • EdDSA + multisigTypeVersion: 'MPCv2' → eddsaMPCv2Callbacks: createEddsaMPCv2KeyGenCallbacks(...) (WCI-895 factory)
  • EdDSA without the flag → existing eddsaCallbacks: createEddsaKeyGenCallbacks(...) (MPCv1, unchanged)
  • ECDSA and onchain paths untouched

Why

• WCI-918 of the WCI-888 plan: consumers opt into EdDSA MPCv2 by passing multisigTypeVersion: 'MPCv2' on the generate-wallet request; MPCv1 remains the default

Dependencies

• Stacked on the WCI-895 PR (the callback factory this routing branch uses). The full chain: bump (chore: bump packages #283) → AWM handler (feat(awm): add EdDSA MPCv2 key generation handler, types and route #282) → ME client (WCI-893) → callback factory (WCI-895) → this PR.

Test plan

• tsc --noEmit clean; ESLint clean
• Default EdDSA (no flag) still routes to MPCv1 path
• multisigTypeVersion: 'MPCv2' routes to eddsaMPCv2Callbacks via the factory
• E2E integration test (WCI-896) exercises the full chain

Ticket: WCI-918

[linear-code]

WCI-918