zipkin-hbase scans backwards

Since row keys for a particular service start at Long.MAX_VALUE at the epoch and
grow towards 0 as time progresses, starting at 0 and scanning until a reversed
timestamp actually finds traces after the specified date, and not before.

Author: @sethp-jive
Fixes #369
URL: https://github.com/twitter/zipkin/pull/369