The test takes 2 mins hereas most other tests in jstests/core take 22 seconds or so. The side effect of this is when the suite runs with randomization, Resmoke ends up consistently running this test at the very beginning of most suites (because the test takes so long) and that hurts test coverage in the passthrough suites because this test isn't being exercised with hooks that have any sort of delay before starting.

We should break this test up. Additionally, it is 1000+ lines long, which is quite long for a test in jstests/core.

The particular suite I saw where this was reducing test coverage was disagg_backup_restore_jscore_passthrough, where we have a hook that waits for a random k tests before running a restore where 1 <= k <= N, and every N tests the hook resets. But because this test almost always runs first, it means that the hook almost always runs after the test has already been executed.