When a $lookup resolves a sharded timeseries view, the ResolvedView may arrive with timeseriesUsesExtendedRange=false because the view was resolved on a different shard
(e.g. after movePrimary relocated system.views) that never received extended-range
inserts and therefore has the per-node in-memory flag unset. We added a workaround to check the local buckets collection, which has the authoritative flag if this shard owns the data. This code can be removed once viewless timeseries are the default in 9.0.