User data in encrypted Vaults

[grumbach]

• Node side Vault Upgrade implementation (previously only supported paying for vault but not accepting updates)
• CLI integration of local disk user data
  • now register list and file list commands show previously uploaded data addresses
• CLI integration of vaults to backup the local user data to disk

Usage: autonomi vault [OPTIONS] <COMMAND>

Commands:
  cost    Estimate cost to create a vault
  create  Create a vault at a deterministic address based on your `SECRET_KEY`. Pushing an encrypted
          backup of your local user data to the network
  load    Load an existing vault from the network. Use this when loading your user data to a new
          device. You need to have your original `SECRET_KEY` to load the vault
  sync    Sync vault with the network, including registers and files. Loads existing user data from
          the network and merges it with your local user data. Pushes your local user data to the
          network
  help    Print this message or the help of the given subcommand(s)

• Vault key generation from EVM secret key signature => meaning apps without access to the key itself but with signing capabilities like metamask or hardware wallets can also use this feature!

AFTER THIS PR USER ONLY NEED TO KEEP TRACK OF 1 SINGLE KEY (EVM key) to access everything Autonomi related:

• register secret key (encrypted in the vault)
• previously uploaded data addresses (encrypted in the vault)
• previously uploaded register addresses (encrypted in the vault)
• vault key (generated from evm key sig)

[grumbach]

Currently all data chunk/registers/vault are priced the same: per address.

[mazzi]

LGTM 🚀
Would be nice to add doc comments and tests on autonomi-cli/src/commands/vault.rs public functions as they are core to the project. Same with other files on autonomi-cli/src/commands/.
WDYT?