Make RangeDeleter correctly handle epoch changes due to shard key refinement

Right now, the range deleter uses the epoch of a collection to uniquely identify it, and if the epoch changes, it will throw out the range deletion tasks for that collection. However, now that refining the shard key changes the epoch of a collection, this logic is no longer correct and will lead to permanently orphaned documents.