feat(PSDK-670): Support external wallet imports, wallet imports from CDP Python SDK

[derek-cb]

What changed? Why?

• Support external 1-of-1 wallet import via BIP-39 mnemonic phrases (12, 15, 18, 21, or 24 words)
• Support import of wallet data exported from CDP Python SDK
• Deprecate Wallet.load_seed method in favor of Wallet.load_seed_from_file
• Deprecate Wallet.save_seed method in favor of Wallet.save_seed_to_file

Testing

Tested via:

• Import of 12, 15, 18, 21, and 24-word mnemonic seed phrases
• Export of wallets generated via mnemonic seed phrases
• Import of wallets generated via mnemonic seed phrases, that were then exported
• Successfully imported wallet exported from CDP NodeJS SDK v0.11.0

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1

[derek-cb]

Next-up: test cases

[derek-cb]

lint changes

[alex-stone]

This is importing a wallet from previously exported wallet data or "creating a new wallet" from a mnemonic seed phrase.

It feels like we should split out the "load" from the "create" flows here? Or is the intent to lazily create the wallet (if one does not exist)? In that world we'd need to be able to check if a wallet already exists when providing the Mnemonic Seed Phrase as well?

@derek-cb @John-peterson-coinbase what are y'alls thoughts here?

[alex-stone]

Edit: See that this is a 2-step plan:
Move WalletData out of the import() method and into its own method (ie, load())

Seems reasonable, although I feel like import would make more sense than import_data for that behavior of taking a mnemonic seed phrase or seed hex, and creating a wallet?

[derek-cb]

ah yes good point. while this is a two-step plan, as you mentioned it doesn't quite make sense in the context of the Python SDK since the existing method is called "import_data". i would propose:

• renaming "import_data" to "import_wallet" ("import" is a reserved method name in Python)
• create a new method called "import_data" for backwards compatibility (that we will remove in a future breaking release) that accepts only WalletData - not the mnemonic phrase - and simply calls "import_wallet".

@alex-stone what do you think?

[alex-stone]

That seems reasonable!

[derek-cb]

@alex-stone committed now