In the process of doing SERVER-112058 we discovered that the function uses the same path for both find or delete depending on what action we're doing.

However, this reveals a problem if we're doing a find since those get wrapped in a writeConflictRetry loop as well. If the loop were to encounter a write conflict, it would abandon the snapshot and potentially cause an existing collection acquisition to have a stale pointer. This has the potential to result in a system crash or undefined behaviour.