Personal split

[jacogr]

Split personal_* RPC into safe & unsafe parts. End-result is that the safe parts are available to dapps as well, which includes

• personal_accountsInfo
• personal_listAccounts
• personal_listGethAccounts

Does the split on the Rust side and re-enables the use of personal_accountsInfo on the dapps side (used for mapping accounts to names)

[tomusdrw]

I'm not sure if any dapps are already relying on personal_unlockAccount or personal_signAndSendTransaction to be exposed.

For backward compatibility we could expose those methods, but slightly modified:

1. Instead of expecting a password to decrypt the key it would expect single-use password.
2. Such password could be generated in secure signer.
   or
3. We can accept any password there
4. Convert it to standard Signing request

Just leaving it here if we ever consider that.

[jacogr]

Found a couple of subtle issues where the initial rush to remove all personal_accountsinfo didn't catch the corner cases. Since the JS side basically moves back to prior to personal-being-completely-locked, it will solve some nigglies in the dapps.

[jacogr]

@gavofyork As discussed, @tomusdrw made the changes so safe is now only listAccounts & accountsInfo. Please review, would like to get this in and humming.

[rphmeier]

Core portion LGTM. Personal looks like it can be easily ported to auto_args now. The signer return values are still blocking the other personal APIs.

[rphmeier]

(would like a UI sign-off as well)

[jacogr]

UI was just a revert of the previous half-fix when it was removed. All dapps tested on this branch.

[jacogr]

@ngotchac Ping.

[ngotchac]

Looks good to me