In the range_deleter_service_test_util, there is a function to register a task with the range deleter. It registers the task as pending and then unsets the pending flag. However, the pending flag is not set on the task in the collection_sharding_runtime_test, so when the task is inserted, it is not marked as pending. This can lead to the update removing the pending flag failing since the range deletion has already completed and the task has been removed.

We need to ensure that the document that is being persisted has the pending flag set before it is unset.