[hbase-spark] Enhance dataframe filters to handle naively encoded short, integer, long, float and double

Currently, the range filter is based on the order of bytes. But for java primitive type, such as short, int, long, double, float, etc, their order is not consistent with their byte order, extra manipulation has to be in place to take care of them correctly.

For example, for the integer range (-100, 100), the filter <= 1, the current filter will return 0 and 1, and the right return value should be (-100, 1]