Transaction Builder

The aforementioned, and still in need of plenty of test fixtures, `TransactionBuilder`.

Anyone is welcome to throw fixtures at it, but, presuming you abide by the API (should be obvious), it should automagically sign them correctly with the private keys provided.
See tests for the intended behaviour.

All standard transaction types are supported including P2SH variants thereof. 

It also needs a `fromTransaction` method for initializing it from an incomplete `Transaction` so you can pass a incomplete `Transaction` around between signers.
I understand that a transaction output can only be spent once. I missed that tx.addInput doesn't prevent the same hash & index combination being added more than once. Then my question becomes who's responsibility should it be? Here in TransactionBuilder or over at Transaction?