SERVER-90992 introduced a collection misuse detector in debug builds. However, this gets hit after the fact and it's a bit of a pain to detect where this is happening.

A scenario we've seen in SERVER-94613 is entering a writeConflictRetry loop with a lock-free collection acquisition. In that case we can trigger a WT snapshot abandonment that would lead to a stale pointer being held.

To prevent this we should add a debug check when entering the WCR loop. This will hopefully detect more dangerous scenarios.