Today the synchronizer expects callers to check for its existence in the CSR and to either call onOplogEntry or to perform the action as shown in this snippet.

However, it turns out that we cancel the current synchronizer execution whenever we perform a clear, which ends up offering the same semantics since the recovery will be retried. In other words, the pattern of calling onOplogEntry for invalidation is unnecessary as the semantics/serialization are exactly equivalent.

We should only have that logic for operations that do not perform a full invalidation which as of 9.0 is only the ones that issue UpdateCollectionMetadataOplogEntry (delta entries).