hRaven Reducer Estimator

Adds new "scalding-hraven" module with an estimator that looks up job history in hRaven to determine the actual amount of bytes reaching reducers. The `HRavenHistory` trait can be added to a `ReducerEstimator` to add functionality for looking up job history, and the `RatioBasedReducerEstimator` does this, scaling the estimate provided by `InputSizeReducerEstimator` based on the past ratio between mapper/reducer input sizes.

This PR also includes a couple other minor changes:
- Using a case class as argument to `estimateReducers` to hold the common reducer estimator info (`flow`,`step`,`predecessorSteps`)
- Add optional `fallbackEstimator` which lets estimators be chained

So far I don't have a story for unit testing hRaven. Any ideas are welcome.
Perhaps, but if it is that generic, how can you compose at all? Seems like this might be a case where bottlenecking on a common subset of information could make it easier to reuse. How can I make use of a `HistoryService[T]` unless I have some kind of `HistoryEstimator[T]`, but those are just black boxes, right?