User impact
The range deleter may indefinitely get stuck if a collection with range deletion tasks is dropped and recreated as a timeseries or view.

Affected versions
This issue does not occur in +6.2 because, since SERVER-65016, dropCollection removes range deletion tasks referring the collection being dropped.

Description
When a moveChunk operation occurs, we register a task on the range deleter to eventually remove orphan documents within that range. During the execution of that task, the range deleter process the task by first performing an AutoGetCollection. Then, checks whether the collection's UUID matches the one recorded when the task was registered. If the UUIDs do not match, the task is removed from the list of scheduled range deletions.

However, if the collection has become a view by the time the task is being executed, the AutoGetCollection will fail with a CommandNotSupportedOnView error, without arriving at the UUID checks. This error is treated as retriable for the range deleter, which results in indefinitely retrying the task.