The default receiveChunkWaitForRangeDeleterTimeoutMS value of 10 seconds is too low for migration_fails_if_exists_in_rangedeletions.js.

Specifically, the test kicks-off migration which will block on range deletion here and then waits for 5 seconds before it turns off the failpoint. By then, 5 seconds have already passed, so only 5 more seconds are left for the range deletion to actually complete.

We should increase it to at least 30 seconds for this whole test.

Also, looking at other tests, which set the suspendRangeDeletion failpoint, it looks like:

• cleanup_orphaned_with_resumable_range_deleter.js
• disable_resumable_range_deleter.js

May also be candidates in order to make them more robust.