Enable customising node policy for datacarrier data size with a -datacarriersize option
qt: Move transaction notification to transaction table model

Move transaction new/update notification to TransactionTableModel.
This moves the concerns to where they're actually handled.
No need to bounce this through wallet model.

- Do wallet transaction preprocessing on signal handler side;
  avoids locking cs_main/cs_wallet on notification in GUI thread
  (except for new transactions)
Update comments in version to be doxygen compatible
Update comments in client version to be doxygen compatible
Merge pull request #5168

023e63d qt: Move transaction notification to transaction table model (Wladimir J. van der Laan)
Merge pull request #5077

2aa6329 Enable customising node policy for datacarrier data size with a -datacarriersize option (Luke Dashjr)
qt: translations update from Transifex
fix a typo
Merge pull request #5187

e743678 fix a typo (Yoichi Hirai)
Merge pull request #5145

484e350 Update comments in client version to be doxygen compatible (Michael Ford)
6395ba3 Update comments in version to be doxygen compatible (Michael Ford)
rpc: Add 'explainrawtransaction' RPC to decode a raw tx with fees, etc.

When decoding raw transactions, it is useful to have information about
the inputs beyond their txid and vout (if this information is available).
This patch adds an RPC analogous to decoderawtransaction, which looks up
the inputs of the raw transaction.

It outputs the following information beyond decoderawtransaction:
  o txout data on all the inputs (everything from gettxout)
  o Total input and output values, and the implied fee
  o the priority of the transaction

Since all this information depends on the inputs being available, if the
utxo lookup fails for any input, the RPC fails, telling the user to use
decoderawtransaction instead.

The JSON output is also contained in a list, unlike decoderawtransaction.
A future extension will be to allow the user to explain several (linked)
transactions in one go, using outputs from earlier transactions when
looking up inputs for later ones. (This is not implemented.)