In SERVER-103990, we replaced waiting for all range deletions to complete with waiting for orphanCleanupDelaySecs to elapse since creation of the most recent range deletion task when transitioning from a config shard to dedicated config server. The range deleter continues processing tasks in the background, consuming I/O resources unnecessarily since collections will ultimately be dropped as part of transitioning to dedicated config server. The purpose of this ticket is to stop the range deleter service at a point where it is safe to do so to help save resources from deleteMany random IO.