fix(example): encrypted seed import

[takenagain]

• Fix EncryptedMnemonicData and Argon2Details parsing
• Show a snackbar if there is an exception. The assumption is that the auth listener overrides the status message containing the exception immediately after it is thrown.
• Validate wallet passwords in komodo_defi_sdk/example app. On native, an exception is thrown in the get_mnemonic RPC if the password contains '<', '>', or '&'

[CharlVS]

• On native, an exception is thrown in the get_mnemonic if the password contains '<', '>', or '&'

@takenagain is this difference observed only when using the get_mnemonic RPC, or is it present everywhere (including startup) where we have to provide wallet/rpc password?

[takenagain]

• On native, an exception is thrown in the get_mnemonic if the password contains '<', '>', or '&'

@takenagain is this difference observed only when using the get_mnemonic RPC, or is it present everywhere (including startup) where we have to provide wallet/rpc password?

It appears to only be the get_mnemonic RPC, and only on native (tested on macOS). On web/wasm, the '&' character in the wallet password does not return the same error, and both sign-in and registration work.

EDIT:
The invalid chars error on native platforms was last modified in the CORS fix PR #2191, and IIRC there was mention of it being for injection attack prevention.

It's implemented in the RPC dispatcher, so it won't throw an error in mm2_main, but for the next RPC request containing the password field, which is currently get_mnemonic (as part of BIP39 validation).