Parlour integration

Not yet for commit.

This how I anticipate the integration working, I'm just not sure the best way to make sure the sqoop job is used as a dependency yet.

I can pass in a tap/source to the Import/ExportSqoopJob, but I'm not entirely sure how scalding will match it up with what gets used in the load.

hm.
we should call this an "upload" function (maybe "sqoopUpload"?) to label it's conceptual similarity to "upload". Personally I think it should be in the upload trait, too, but I'm open to arguments against that. It's just that currently our tasks are grouped by pipeline stage.