[reproducible attached]

The recipient of a migration in v4.4 with FCV 4.2 always stalls for orphanCleanupDelaySec (excluding the very first migration, because the collection is not known).

The flow is the following: in case of FCV v4.2, the migration destination manager calls into beginReceive that unconditionally schedules a range deletion for the chunk being received waiting for the configured delay for secondary queries.

This results in all migrations stalling at least for orphanCleanupDelaySecs even when there is no orphaned document to remove.