[tracking] Key generation readiness

[cwgoes]

dependencies:

• [x] https://github.com/anoma/namada/issues/70
• [x] https://github.com/anoma/namada/pull/2088
• [x] Some interface work presumably, but I didn't find any issue for it /cc @jurevans @mateuszjasiuk @emccorson - We are moving to SDK key generation in https://github.com/anoma/namada-interface/issues/182 - this is assigned to @mateuszjasiuk NOTE Ledger can already generate keys via the extension, any maintenance would simply be to update dependencies as they change
• [ ] https://github.com/anoma/namada/issues/2025 by @murisi (ditto, please link/make an issue)
• [x] https://github.com/anoma/namada/issues/2067

---

This issue tracks feature-completeness of key generation. Key generation is feature-complete if and only if:

• Users can generate keys using the Namada CLI (which should use the same code as the SDK uses - DRY)
  • Manually (random mnemonic)
  • Using the Ledger hardware wallet
• Users can generate keys using the Namada interface
  • Manually (random mnemonic)
  • Using the Ledger hardware wallet
• Users can use these keys to generate appropriate signatures as required for genesis transactions and afterwards
• We're confident that key generation is secure and final (no further changes)
• All key generation-related code is tested, believed to be complete, and audited by at least two people other than the author

Please add any dependencies that you believe are necessary to meet these requirements in the list above.

related: https://github.com/anoma/namada/issues/1950