Negative numbers not properly converted in ABI encoding

Ignore round and curly brackets in strings for indentation level

cmd/geth: fix the keystore path in the accounts help text

cmd/geth: truly randomize console test RPC endpoints

console: fix windows console colors

When converting a negative number e.g., -2, the resulting ABI encoding
should look as follows:
fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe.
However, since the check of the type is for an uint instead of an
int, it results in the following ABI encoding:
0101010101010101010101010101010101010101010101010101010101010102. The
Ethereum ABI
(https://github.com/ethereum/wiki/wiki/Ethereum-Contract-ABI) says,
that signed integers are stored in two's complement which should be
of the form ffffff.... and not 01010101..... for e.g. -1. Thus, I
removed the type check in numbers.go as well as the function S256
as I don't think they are correct. Or maybe I'm missing something?

eth: don't accept transactions until we sync up with the network

eth/downloader: adaptive quality of service tuning

eth/downloader: make fast sync resilient to critical section fails

core: add missing lock in TxPool.GetTransaction

Fixes #2650

cmd/geth: make console tests more robust

* use --port 0 to avoid p2p port conflicts
* use --maxpeers 0 so it doesn't connect to bootstrap nodes
* use geth.expectExit() to wait for termination

This makes "geth js file.js" terminate again.

eth/downloader: ensure cancel channel is closed post sync

eth/downloader, trie: pull head state concurrently with chain

cmd, console: split off the console into a reusable package

core, core/state, trie: enterprise hand-tuned multi-level caching

core/state: return the starting nonce for non-existent accs (testnet)

eth: enable bad block reports

misc: fix spelling mistake

eth/api: fixed GetCompilers when there is no error creating Solc

common/compiler: support relative path to solc

We used to have reporting of bad blocks, but it was disabled
before the Frontier release. We need it back because users
are usually unable to provide the full RLP data of a bad
block when it occurs.

A shortcoming of this particular implementation is that the
origin peer is not tracked for blocks received during eth/63
sync. No origin peer info is still better than no report at
all though.