We have some existing tests that cover time-series operations but which test the operations while exercising much bucket reopening.

For example, timeseries_deletes_and_insert.js tests non-metadata filter deletes, but because it doesn't insert enough measurements to archive/close buckets, it didn't allow us to detect SERVER-94559.

We should increase our coverage of time-series operations in the presence of heavy bucket reopening. Two possible ways of going about this include:

1) Creating a new time-series passthrough test that triggers a lot of bucket reopening;

2) Add knobs in the config fuzzer related to bucket reopening/time-series collections

The second approach might be more straightforward