Ensure that correct data about spending transaction is present in JSON

InputScriptPubKeys from different transactions could mix and corrupt
validation context. PubKeys moved from list to dictionary of lists,
with transaction hash as key.

When node accepts transaction or receives block, it tries to load all
inputs to mempool. Trying to load zero-inputs to mempool leads to
corruption - valid transaction may be removed from mempool during
conflicts check. To prevent this, inputs selection algorithms modified
to ignore zero-inputs. Conflicts check ignores them too.

Light wallet feature mostly depends on wallet's source code, which is
already modified.

If fee type is "Included", fees is charged from receiver. If fee
type is "Extra", fee is charged from sender.

If fee type is "Included", fees is charged from receiver. If fee
type is "Extra", fee is charged from sender.

Transaction fee is validated before accepting transaction to mempool

Only confirmed coinstake transactions are passed to transaction builder
as available inputs.
Inputs from coinstake transactions are not grouped to avoid spending
all coins avaliable for staking.