les: fixed selectPeer deadlock, improved request distribution

core: fix race condition in WriteMipmapBloom

console: fix error message in faux JSON-RPC responses

accounts/abi: support custom int slice types

Check for slice in type as well and adapted test case as arrays
also store its types.

On solidity contract I have "uint32 []" type, when abigen creates Go
bindings - they are also "[]uint32" type on Go side. Even though it
looks like it should work - the actual type of the data coming from
the chain is of type " []*big.Int".

When executing contract function from Go side - getting unmarshal error:
abi: cannot unmarshal []*big.Int in to []uint32

The fix is to create array with the correct type

This fixed the issue reported in: https://github.com/ethereum/go-ethereum/issues/2802

The message was used as both key and value in the error object.
This only affected unusual errors with no error code.

all: fix spelling errors

all: clean up lint issues, remove more dead code

mobile: rename passphrase signing method to avoid Swift rewrite

The crash when compiling stdin was fixed in solc 0.3.6 (released
2016-08-10). While here, simplify the test so it runs with any solc
version.

Fixes #3484. The byte code was different for each run because recent
solc embeds the swarm hash of contract metadata into the code. When
compiling from stdin the name in the metadata is constant.

core/types: remove redundant SignECDSA wrappers, rename to SignTx

core/types: dependency cleanup

This removes the core/types -> leveldb dependency.

This significantly reduces the dependency closure of ethclient, which no
longer depends on core/vm as of this change.

All uses of vm.Logs are replaced by []*types.Log. NewLog is gone too,
the constructor simply returned a literal.

params is imported by leaf-ish library packages and should not pull in
the p2p stack.

les/flowcontrol: using proper types for relative and absolute times

build: finally settle on empty iOS ObjC package prefixes

Account management API polishes

core,cmd/utils: bugfix for ropsten dump imports

The run loop, which previously contained custom opcode executes have been
removed and has been simplified to a few checks.

Each operation consists of 4 elements: execution function, gas cost function,
stack validation function and memory size function. The execution function
implements the operation's runtime behaviour, the gas cost function implements
the operation gas costs function and greatly depends on the memory and stack,
the stack validation function validates the stack and makes sure that enough
items can be popped off and pushed on and the memory size function calculates
the memory required for the operation and returns it.

This commit also allows the EVM to go unmetered. This is helpful for offline
operations such as contract calls.