Add a few test cases to data-driven script tests and add data-driven transaction tests. #1651

They are largely useless, but they do double-check a few things that could be useful for new implementations. (and quite a few of them are duplicated, but I don't feel like looking into which ones).

Now with data-driven transaction tests which consist of a list of inputs, and a serialized transaction. Again, the data-driven transaction tests are more targeted at alternative implementations than the reference client.

Also pulled in a commit to make test_bitcoin useful when it fails (otherwise you have no idea why it failed, it just says failed and you have to scroll back through a ton of crap to find it).

quick ACK (== I scrolled through them for a sanity check, but did not stare hard at each one)

The following is an automatic comment from the Bitcoin Pull Tester. If you believe it is in error, please contact jenkins@bluematt.me

This pull passed automatic sanity-tests! This means it merges cleanly onto current master, builds and unit-tests pass You can find the test log and build output at http://jenkins.bluematt.me/pull-tester/3495738c2920c1cfa96a5278c797903f8eadb8d6

Temporarily closing to add more tests which are waiting to push.

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/da9e86c3b6cfdd13ed71744a082df94de1f3f41f for binaries and test log.

ACK (compiles and runs nicely on my Mac)