feat: add ledger, stronghold and keychain into cli

[lmoe]

Description of change

Adds a more secure layer into the wasp-cli.

It is based on the wasp-wallet-sdk library
Which is based on the iota-sdk native library

This feature introduces Ledger and Stronghold wallet providers.

Alternatively, the user can choose to remain using the common seed - but it will now be stored in the OS Keychain instead of the wasp-cli.json. The seed will be loaded into a more secure encrypted in-memory vault at runtime.

Starting from this version, each user is required to have the iota_sdk library next to the wasp-cli. Prebuilt releases are available here and are shipped with wasp-cli releases as well.

Type of change

Choose a type of change, and delete any options that are not relevant.

• Bug fix (a non-breaking change which fixes an issue)
• Enhancement (a non-breaking change which adds functionality)

How the change has been tested

The most delicate parts are in the two referenced dependencies.

The Go library has tests, which are to be found here
The Rust native lib does not have tests yet.

[dessaya]

So... who is going to validate this? 🤣

[lmoe]

I did! Seems to work fine. :D

[dessaya]

Suggested change

	log.Printf("In memory seed saved in the keychain.\n")
	log.Printf("In-memory seed saved in the keychain.\n")

[Dr-Electron]

After some weeks of working with this branch I didn't really have any major problems.

Some notes tho:

• If I run init -c wasp-cli.json no config is created. It uses my keychain as default. But maybe a wasp-cli.json with that info should at least get generated. This allows me to specify a different config path with the -c option on init so that I can use that file for all future commands
• Even if I change the scheme to stronghold the cli still seems to look for the keychain and store stuff there. Everything is working with stronghold just needs som cleanup I guess to not check for keychain stuff 🤔