During development of SERVER-109829 we forcefully made almost all lock-free reads use an instantiated opened collection. This type of collection can be the result of a PIT read resulting in a new Collection instance being created for the duration of the WT snapshot.

Doing this revealed that timeseries with extended date ranges can result in the wrong query execution if the targeted collection is dropped but read at a previous timestamp. The boolean flag maintaining this is only stored in-memory and set only when a timeseries insert occurs. When the collection is dropped this information is lost and so the next time we access that collection we'll recover it from the durable metadata.

However, this data doesn't contain whether the collection has extended dates, which will lead to using the invalid set of optimizations that can only be done when there are no extended dates present.