Prevent Direct Transfer from timing out migrations with many entities

On https://gitlab.com/gitlab-com/dev-sub-department/section-dev-request-for-help/-/issues/341#note_2223253953, it was identified that Direct Transfer is timing out migrations even when they are still running.

The issue arises when entities take longer than 24 hours to begin processing. This delay causes the BulkImports::StaleImportWorker to mark these entities as timed out.

This problem is more likely to occur during migrations involving a large number of entities. Since the Direct Transfer process only handles five entities at a time, entities may not be processed within the 24-hour window. As a result, the BulkImports::StaleImportWorker flags these entities as timed out, even though the migration process itself is still ongoing which does not justify BulkImports::StaleImportWorker marking the entities as timed out.

Proposed solution

To prevent BulkImports::StaleImportWorker from marking the entities from migrations that are still running fine as timeout. One solution is to change the updated_at of the entities that haven't started from time to time.