feat/944 - Extension updates - BIP44/Zip32/Ledger/Masp

[jurevans]

Resolves #944
Resolves #1154

• Include Extension/SDK versions in Settings
• Add SDK version to Namadillo settings
• Zip32 should derive default shielded accounts from ed25519 private key (like Namada CLI) with default account
  • Add SDK package functionality to do this from either a Seed (64 bytes) or SK (32 bytes)
    • sdk.keys.deriveShieldedFromSeed()
    • sdk.keys.deriveShieldedFromPrivateKey()
• Add BIP44 path form to Mnemonic Import (Advanced)
  • Combine Bip39 passphrase and path to Advanced view
  • Generate shielded account from Zip32 version of path (makeSaplingPathArray(path))
• Add BIP44 path form to Ledger Import (Advanced)
  • NOTE I hooked up shielded keys to our Ledger class, though it won't be useful until we have Zip32 derivation on Ledger. This gives the SDK the interface to use, but we'll want to hook it up to the UI after Zip32 is added!
• Bump extension version
• Hook up Viewing Key
  • Update styles for Viewing Key (See screenshots at bottom)
• General UI Styles (will follow-up after this PR to finish the styles prior to release)

TODO

• Add BIP44 path form to Mnemonic Generate (Advanced) - We didn't specify this as a use-case, but it could be added as well - we should discuss that it is also possible to specify a BIP39 passphrase here, though we had copy indicating that it was only to support the same accounts in Namada CLI that used them. If someone used a BIP39 passphrase there, I feel like they could use it on their generated BIP39 seed and not just the imported one.
  • Generate shielded account from Zip32 version of path (makeSaplingPathArray(path))
• We can now generate shielded keys from a private key, so this can be added to Import -> Private Key using a default path
• Regenerate docs if sdk or types changes! NOTE This should be in a separate, SDK-release PR, as other PRs will affect the docs too and it creates too much noise for an already large PR

Screenshots

NOTE Styles are still in progress...

Advanced Menu (Import Mnemonic):

Custom Derivation Path:

Bip39 Passphrase:

Keychain & SDK versions:

SDK version in Namadillo:

Path displayed (only when a custom path was specified):

Designs

Updated designs for Viewing Key:

FIGMA:
https://www.figma.com/design/NFyHbLZXBSl3aUsMxtffvV/Namada-End-User-Interface-V1.0-%2F-Phase-1%3A-Block-Party?node-id=6361-75215&node-type=canvas&t=cJGwuzI3Q8soSDus-0

[jurevans]

For signing with transparent keys, all of these values are expected to be present! Ledger does not have Zip32 paths as of yet

[mateuszjasiuk]

This works great!

I have couple of minor UI/UX comments.
I personally do not like these numeric input arrows :D

Also maybe we can reduce font size or sth so we do not see the scroll.

I'm curious if it makes sense to enable "advanced" button only if we are in Step 2 of HW Wallet import flow. Not sure xd

[jurevans]

I'm curious if it makes sense to enable "advanced" button only if we are in Step 2 of HW Wallet import flow. Not sure xd

Thanks! Yeah some of these style things I will fix in a follow-up PR before release, I think those are all good suggestions!

[jurevans]

I have couple of minor UI/UX comments.
I personally do not like these numeric input arrows :D

FYI: Tracking these comments in #1229 !