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
So first, let me say that I'm not a big fan of the last level of packages in the `core` project. We seem to have too many packages that just contain one class, which makes that last layer redundant.

That said, for better or worse, the current code tends to put the tasks themselves in the `task` package, but all the supporting functionality for those tasks goes into a random bunch of separate packages. E.g., the upload task is in `task`, but all the supporting logic is in `upload`. The `load` task in in `task`, but all the supporting functionality is spread over other packages. Etc.

Sqoop has so far avoided this because all the supporting functionality is in a separate project. But no longer. IMO this should go in a `sqoop` package.