The `random_moveChunk_refine_collection_shard_key.js` test concurrently runs moveChunk and refineCollectionShardKey, with the latter causing migrations to abort or be interrupted.

The test infrastructure allows for some expected errors that won't cause the test to fail if the moveChunk fails due to the abortMigrations of the refineCollectionShardKey.

If the abortMigrations interrupts when the moveChunk is waiting for the future of the range deleter to complete, the error is not accepted, and the test fails.

The goal of this ticket is to make the test robust to this error.