Add TimeRange support into Increment to optimize for counters that are partitioned on time

In many use cases of increments, a given counter is only incremented during a specific window of time (ie. the counters are partitioned/sharded by time).

With this kind of schema, you are constantly creating new counters. When a new counter is "created" (incremented the first time) you will always end up looking at a block from every file in the region because no previous value will exist. However, with the new TimeRange optimizations that skip files if they don't contain values of the TimeRange you're interested in, we could utilize that information to optimize the Get within the increment.

This would be optional and an addition to the Increment class.