When $lookup targets only local shard for sub-pipeline, it performs local reads.

However, if the targeted collection was already read by the same query, it is possible that some storage snapshots are left inside OperationContext, Transaction, etc. that will prevent the query from reading the latest data.

We need to make sure that there is no discrepancy between routing info that we use and the data that we read.