SERVER-75445 revealed some issues in the moveChunk + timeseries delete/update tests:

1. The update/delete filter didn't match any records.
2. The test setup with the mirrored non-sharded, non-timeseries collection did not take into account some isolation behaviors that can occur - namely that a record can get skipped during a deletion or update on the sharded collection due to the background moveChunk operations. This means that the two collections do not always have the same contents at the end of the test.

SERVER-75445 resolves these issues in random_moveChunk_timeseries_deletes.js by fixing the delete filter and relaxing teardown validation on the collection's contents. When applying the same fixes to the update test, the test runtime becomes very long and causes timeouts. We need to fix the two issues above and also determine the cause of the timeouts (hopefully we can just tweak the test configuration to reduce runtime).