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
In the context of unit testing in maestro core, we could combine them into one or two. My mind was setup on what I wanted to see in the etl test. There I would like to give users this flexibility because I expect to hear things like - "This works with in-memory but behaves differently with Oracle"