Godeps: pull in ethash with the big endian build fix

cmd/evm: added --create flag indicating the exec code is to be created

cmd/utils: add space between "to" and filename

This fixes an issue if you wanted to test out code deployment rather
than running a piece of code with an argument. This solves it by adding
a --create flag that indicates the Create function should be used rather
than the Call function.

This also adds a statedb.commit call so that the proper state can be
dumped when requested using the --dump flag.

accounts/abi: fix uint64 upper range encoding.

core/state, eth: Updated suicides objects when tracing transactions

core: improved chain db performance by using sequential keys

eth/downloader: fix occasional fast sync critical section test fails

Consensus rules dictate that objects can only be removed during the
finalisation of the transaction (i.e. after all calls have finished).
Thus calling a suicided contract twice from the same transaction:
A->B(S)->ret(A)->B(S) results in 2 suicides. Calling the suicided
object twice from two transactions: A->B(S), A->B, results in only one
suicide and a call to an empty object.

Our current debug tracing functionality replays all transaction that
were executed prior to the targetted transaction in order to provide
the user with an accurate trace.

As a side effect to calling StateDB.IntermediateRoot it also deletes any
suicides objects. Our tracing code never calls this function because it
isn't interested in the intermediate root. Becasue of this it caused a
bug in the tracing code where transactions that were send to priviously
deleted objects resulted in two suicides rather than one suicide and a
call to an empty object.

Fixes #2542

cmd: fix CLI package deprecation warnings

cmd/geth: codegansta/cli package renamed to urfave/cli

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