KeysSearcher doesn't filter results by key range

In 3.0 the check in KeysSearcher to validate that a hit from the index is falls within the key range of command being executed was ommitted. The effect of this can be observed in a vnode cluster with > 1 node where nodes contain non-contiguous ranges.

Because of the lack of range checking, each range command sent to a given replica will return all matching rows, resulting in duplicates in the result set (i.e. one duplicate per merged range).