Full coverage of _test.py by unit_test.py and integration_test.py

1) clean and reorganize fixture files
2) add raw transactions comparison for each scenario (to cover test_outputs)
3) add test of base58_check_decode in unit tests vector
4) add test books in integration tests:
- these tests can be skipped by using `--skiptestbook`. For instance to skip mainnet book test use `py.test test/integration_test.py --skiptestbook=mainnet`. (https://github.com/JahPowerBit/counterpartyd/blob/develop/test/conftest.py#L44)
- reparsing is done in memory database (40% faster on my dev server).
- these tests don't generate books files with credits/debits but use check_movements_hash. If one hash don't matches, test raise an error and show the credit/debit line where there is a difference. (see: https://github.com/JahPowerBit/counterpartyd/blob/develop/test/util_test.py#298)

scenario_1, and its multisig brother scenario_2 come from _test.py, so with the raw transactions comparison I added, we cover all _test.py tests. 
@PhantomPhreak I waiting your go to remove _test.py.

Next steps: 
- add mock function for bitcoin.multisig_pubkeyhashes_to_pubkeys() (because it uses searchrawtransactions)
- add scenarios for 2 of 2 and n of 3 multisig transactions
- continue to populate unit test vectors to cover all transactions