Making the testing Sqoop cascades easier

Got rid of setting MapRedHome in the Cascade
Extracting out the Database specific piece.
Providing a fixed function for data setup and cleanup
Yeah, but the specs tests are run concurrently by default. We can disable that, but I would prefer our test frameworks to handle being run concurrently unless doing so is too much work.

In this case I am imagining the underlying framework passing in some unique integer into each test, which the setup and cleanup functions use to create and remove unique table names, ensuring the tests don't step on each others toes.

I don't think it's absolutely necessary to do this, and if you don't want to bother, that's fine. But if you think you can do it quickly while the test code is all in your head, than that would be great. If not, that's fine too.