Declare explicit dependency between the test cases, to fix spurious test failure
Declare explicit dependency between the test cases, to fix spurious test failure

This test is a bit naughty in that forkscsv_dumpforks_test expects a 'segwit' output for the main network.
This 'segwit' fork is configured in forkscsv_read_test, and so the test works fine as long as that case is executed first.
In my own tests this always seemed to be the case, but Travis seems to show up this dependency quite well.

The test would presumably also work without the explicit dependency if the segwit fork data were built in to the client.
That has not been done in order to keep somewhat unrelated changes in the application to a minimum.

BitcoinUnlimited/BitcoinUnlimited,Justaphf/BitcoinUnlimited,Justaphf/BitcoinUnlimited,BitcoinUnlimited/BitcoinUnlimited,BitcoinUnlimited/BitcoinUnlimited,Justaphf/BitcoinUnlimited,BitcoinUnlimited/BitcoinUnlimited,Justaphf/BitcoinUnlimited,BitcoinUnlimited/BitcoinUnlimited,BitcoinUnlimited/BitcoinUnlimited,Justaphf/BitcoinUnlimited,Justaphf/BitcoinUnlimited