feat: allow keychain interactions without a password

[achingbrain]

Possibly contentious PR, but go-ipfs does not require a password to list or generate keys but js-ipfs does. This prevents us from having interop as the behaviour is different.

This PR sets a silly default password to enable this but I'm not 100% convinced any of this is a good idea.

Needed for the tests in ipfs/js-ipfs#1548 and ipfs/interop#35 to pass.

[vasco-santos]

In my honest opinion, keychain interactions should be protected by a password, as we have in JS land. However, afaik there are no specs for this.

But since we have a different approach from the GO team, we should discuss together and decide if JS should abdicate from this feature, or if they should add this feature on their side.

What do you think?
@libp2p/javascript-team
@libp2p/go-team

[achingbrain]

My feeling is that requiring the password for all interactions is a bit heavy handed - the password is not required by the code to list keys in the keychain for example.

[bigs]

perhaps a flag to allow a user to set a password, similar to how SSH prompts for a password but doesn't require it?

[daviddias]

What if the default password is just empty string?

[achingbrain]

The code later enforces that the password should be 20+ characters long.

[achingbrain]

Closing because this is very old and probably not a good idea.