Camus in production

I apologize for a massive pr. This pr gets us ready with a jar that can be deployed in production.
Included in it:
- Camus
  - Update to MessageDecoder to use joda time in order to parse both time format according to iso format, formerly this broke with multiple time formats which we send on kafka
- Sweeper
  - Custom mapreduce jobs (straightforward in their implementation just to join all files together)
  - Add support for traversing topics
  - Add support for putting in per hour files as opposed to per day
- Cleaner
  - Custom cleaner to delete files more than one hour old including daily and monthly folders. We don't want to keep already processed files in raw directory. 

please review @drdee @airhorns @honkfestival 
I think patching a class should be avoided though, thats the point. It will create merge conflicts as we upgrade and couples our entry point to the internal structure of the system. So I would say a one method class with this method in it is better. That said, Azkaban can do anything! You can make a `command` type jar that just does java -jar and other stuff. I dont understand the benefits of having the same jvm do the work, because it has to fork anyways, it couples the java versions and environments, and afterwards we could never containerize. Unix > Java.