The online archive procedure sets "control.closed" to true on bucket documents as a way to tell the server that no writes may occur on these buckets.

We need to validate that the server respects this flag in the presence of logical inserts, updates and deletes concurrently with bucket reopening and external writes of "control.closed".

Design sketch for the test:
Concurrently set "control.closed": true using findAndModify to random buckets. Both open buckets actively being written to and buckets actively being reopened. Cache the result of findAndModify and validate the buckets at the end of the test that no further writes have been performed on them.

We should use an existing test as a base, timeseries_insert_idle_bucket_expiration.js does a lot of reopening. The question is if we need two tests to ensure we have sufficient coverage for both the open bucket case and the reopen case.