Start work on scalding-lingual support.

Lingual has some nice features that would be nice to have for some small adhoc jobs and especially with the Scalding REPL.  These changes do not contain the repl code yet(coming in a future pull request) but attempt make lingual a bit easier to use with Scalding libraries and allow for scalding code to still be written and run with a Lingual job.

This code also does not support nested functions yet in queries like thrift.  Should be technically possible based on conversations with the Lingual team.


This (and openFile, for example) have no dependency to the rest of the code. Consider moving into the class object so it stays that way, and it's clear what are just short utilities, and what aren't?

Either that or make them private. I'm questioning the utility of making public something so simple, though I understand the internal utility.