SERVER-55429 added a timeout when waiting for range cleanups in the recipient of a migration, currently the default timeout is 10 seconds, which seems to be a very short period of time for the concurrency suites.

We could solve this by either ensure we have a script that automatically retry the migration (like for example network_error_and_txn_override.js) and adding the string "operation was interrupted" to the error message, or find a more suitable default value for this parameter.