Fix Version/s: 1.2.1
There are many cases where getRangeSlice creates more
RangeSliceCommand than it should, because it always creates one for each range
returned by getRestrictedRange. Especially for CL.ONE this does not take
the replication factor into account and is potentially pretty wasteful.
A range slice at CL.ONE on a 3 node cluster with RF=3 should only
ever create one RangeSliceCommand.