Shutting down geth prints hundreds of annoying error messages in some
cases. The errors appear because the Stop method of eth.ProtocolManager,
miner.Miner and core.TxPool is asynchronous. Left over peer sessions
generate events which are processed after Stop even though the database
has already been closed.

The fix is to make Stop synchronous using sync.WaitGroup.

For eth.ProtocolManager, in order to make use of WaitGroup safe, we need
a way to stop new peer sessions from being added while waiting on the
WaitGroup. The eth protocol Run function now selects on a signaling
channel and adds to the WaitGroup only if ProtocolManager is not
shutting down.

For miner.worker and core.TxPool the number of goroutines is static,
WaitGroup can be used in the usual way without additional
synchronisation.

internal/debug: also rename debug_startTrace to debug_startGoTrace

Also reduce log messages a little bit.

This was missing from the previous change.

internal/debug: rename debug_trace to debug_goTrace

Reduces confusion with EVM execution tracing methods.

cmd/geth: fixed to use proper version string for output

p2p/discover: prevent bonding self

Make the README suck less :P

Geth release oracle

eth: add personal_importRawKey

Provide a public accessor for ChainConfig

This is necessary for external users of the go-ethereum code who want to, for instance, build a custom node that plays back transactions, as core.ApplyTransaction requires a ChainConfig as a parameter.

cmd: add a `--fakepow` flag to help benchmarking database changes

accounts/abi: refactored ABI package

eth/filters: ignore logs that don't match filter criteria on chain reorg

core, eth: added json tag field for proper unmarshalling

accounts/abi/bind, eth: add contract non-existent error

accounts: disable file system watch on linux/arm64

Improve Address test coverage

cmd/geth, jsre: improve the js command

According to our own instructions the genesis config attribute should be
"config". The genesis definition in the go code, however, has a field
called `ChainConfig`. This field now has a `json:"config"` struct tag so
that the json is properly unmarshalled.

This fixes #2482

cmd/bootnode: fix -genkey, add logging options