This fixes a few uses of unkeyed Body literals which go vet was
complaining about.

all: update license information

cmd/utils: strip excessive whitespace from api command line arguments

eth: fix single transaction tracing (run prev mutations)

eth: add chaindbProperty to debug API (+ console fixes)

This makes web3 internals like _requestManager invisible.

accounts: disable filesystem notifications on iOS

jsre: print BigNumber objects with custom constructor as number

cmd/utils: fix accounts merge error on console unlock

accounts: cache key addresses

cmd/gethrpctest: add missing chain configuration config field

- Sign takes common.Address, not Account
- Import/Export methods work with encrypted JSON keys

Text files created on Windows typically have \r\n line endings.
Trim them when reading password files.

In order to avoid disk thrashing for Accounts and HasAccount,
address->key file mappings are now cached in memory. This makes it no
longer necessary to keep the key address in the file name. The address
of each key is derived from file content instead.

There are minor user-visible changes:

- "geth account list" now reports key file paths alongside the address.
- If multiple keys are present for an address, unlocking by address is
  not possible. Users are directed to remove the duplicate files
  instead. Unlocking by index is still possible.
- Key files are overwritten written in place when updating the password.

- Manager.Accounts no longer returns an error.
- Manager methods take Account instead of common.Address.
- All uses of Account with unkeyed fields are converted.

The account management API was originally implemented as a thin layer
around crypto.KeyStore, on the grounds that several kinds of key stores
would be implemented later on. It turns out that this won't happen so
KeyStore is a superflous abstraction.

In this commit crypto.KeyStore and everything related to it moves to
package accounts and is unexported.

These changes make prompting behave consistently on all platforms:

* The input buffer is now global.
  Buffering was previously set up for each prompt, which can cause weird
  behaviour, e.g. when running "geth account update <input.txt" where
  input.txt contains three lines. In this case, the first password
  prompt would fill up the buffer with all lines and then use only the
  first one.

* Print the "unsupported terminal" warning only once.
  Now that stdin prompting has global state, we can use it to track
  the warning there.

* Work around small liner issues, particularly on Windows.
  Prompting didn't work under most of the third-party terminal emulators
  on Windows because liner assumes line editing is always available.