After SERVER-130440, after enabling Authoritative Shards CRUD we:

1. Interrupt all non-authoritative refreshes in the FilteringMetadataCache.
2. Interrupt all ongoing SSCCL OperationContexts.

However it's possible that the FilteringMetadataCache started a SSCCL load, but that load still has not created an OperationContext (i.e. it has not yet reached before this line). In this case it will be interrupted neither by (1) nor (2), so it can still try to read from config.cache.* which setFCV will concurrently drop, which can cause it to hit tassert 7032350. (See attached repro)

Besides the tripwire assert, this should be harmless but we'd prefer to guarantee no SSCCL loads can occur under Authoritative Shards.