Add new "bitcoin-tx" command line utility

This is a simple utility that provides command line manipulation of a hex-encoded TX.  The utility takes a hex string on the command line as input, performs zero or more mutations, and outputs a hex string to standard output.

This utility is also an intentional exercise of the "bitcoin library" concept.  It is designed to require minimal libraries, and works entirely without need for any RPC or P2P communication.

The command line help provides a list of the mutations available:
```
Usage:
  rawtx [options] <hex-tx> [commands]  Update hex-encoded bitcoin transaction
  rawtx [options] -create [commands]   Create hex-encoded bitcoin transaction

Options:
  -?                      This help message
  -create                 Create new, empty TX.
  -json                   Select JSON output
  -regtest                Enter regression test mode,instantly.
  -testnet                Use the test network

Commands:
  delin=N                Delete input N from TX
  delout=N               Delete output N from TX
  in=TXID:VOUT           Add input to TX
  locktime=N             Set TX lock time to N
  nversion=N             Set TX version to N
  outaddr=VALUE:ADDRESS  Add address-based output to TX
  outscript=VALUE:SCRIPT Add raw script output to TX
  sign=SIGHASH-FLAGS     Add zero or more signatures to transaction
      This command requires JSON registers:
      prevtxs=JSON object
      privatekeys=JSON object
      See signrawtransaction docs for format of sighash flags, JSON objects.

Register Commands:
  load.NAME=FILE         Load JSON file FILE into register NAME
  NAME=JSON-STRING       Set register NAME to given JSON-STRING


```

I'd rather not see big "convert the entire internal structure to some map/vector type" methods. They don't add anything, as the caller (or whoever you're passing the map/vector to) still needs a dependency on UniValue, so they might as well use UniValue's own accessor methods (operator[], ... maybe UniValue needs iterators for the array case).

The only place where they seem actually used is as a type-check, where is* instead of get* could be used.