README: fix build->built typo

(cherry picked from commit e271fd57132763f39c6993a35e6c063aac3af4f1)

cmd, common, console, eth, release: drop redundant "full"s

eth: separate common and full node-specific API and backend service

cmd/geth: fix the import error message

cmd/geth: include the error message on import failure

Revert faulty DAO soft-fork

This reverts commit 7a5b571c.

This reverts commit c4de2893.

This reverts commit ba784bdf.

This reverts commit 1e3a7d4f.

core: update the DAO soft fork proposal to the final block

DAO soft-fork

web3ext: Remove old natspec Admin_JS stubs

This stops them from showing up on the javascript console.

build: add ci.go, use it everywhere

The new build script, ci.go, replaces some of the older shell scripts.
ci.go can compile go-ethereum, run the tests, create release archives
and debian source packages.

This implements a generic approach to enabling soft forks by allowing
anyone to put in hashes of contracts that should not be interacted from.
This will help "The DAO" in their endevour to stop any whithdrawals from
any DAO contract by convincing the mining community to accept their code
hash.

README, core, rpc: Fix typos

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