Paged Range Slice queries with DISTINCT can drop rows from results

If we have a partition where the first CQL row is fully deleted (possibly via TTLs), and that partition happens to fall on the page boundary of a paged range query which is using SELECT DISTINCT, the next live partition after it is omitted from the result set. This is due to over fetching of the pages and a bug in trimming those pages where overlap occurs.

This does not affect 3.0+.