Hardware Authenticators not compatible with KvStore

[fmorency]

One can create/import a hardware authenticator MANY identity when using a kvstore backend. The application should not display the option to the user as the kvstore backend does not currently support hardware authenticator.

[stanleyjones]

@fmorency Question on implementation here...

Technically, we don't need to communicate with the idStore once the identity has been created and/or retrieved. Should we:

1. Disable the "Hardware Authenticator" creation/import option if the selected neighborhood doesn't support idStore but still allow the user to use a previously created/imported identity on a non-idStore neighborhood.
2. Fall back to a neighborhood that does support idStore if the selected neighborhood doesn't (i.e. create/import the ID on the Manifest Ledger unless otherwise specified).
3. Disable Hardware Authenticator based identities completely (i.e. require the user to select a different identity) if the selected neighborhood doesn't support idStore.

Those are in rough order of my preference.

[fmorency]

@stanleyjones

I prefer 3. as the less risky approach until we can manage HSM through a 3rd party such as Web3Auth.

1. I think it can be confusing for users and might result in unwanted operations. The user experience is of utmost importance here.
2. I don't like the idea of server X, e.g., kvstore, depending on a non-specific server Y, e.g., leger, for identities.
3. This is the way.