Merger puts tasks 'In-Progress' for each task type that exists parallely (MAPCO-4446)

If exists, TilesMerger pulls a task for each task type, if tasks exist then all but one are "lost" and get a status of In-Progress.

The relevant code is in the MainRunner file:
https://github.com/MapColonies/GpkgMerger/blob/653bdd5b9e4a17823d70ea03bbf751198c7944fc/MergerService/Runners/MainRunner.cs#L36-L40

phenomenon:
Once three ingestion processes are in parallel, tasks from all ingestion processes are moved to status In-Progress, although the merger does not work on them.

To Reproduce
Run multiple (at least 2) ingestion jobs with different ingestion types with existing tasks. (swap, new, update).

Actual behavior
Merger moves tasks to In-Progress although not working on them.

Expected behavior
Merger will "mark" only one task as In-Progress and work on it.

Commencez par MergerService/Runners/MainRunner.cs, en particulier les lignes 36-40, et reproduisez le problème en exécutant au moins deux jobs d’ingestion avec des types différents tels que swap, new et update. Suivez les tâches qui sont marquées comme In-Progress lorsque plusieurs tâches existent. C’est terminé lorsque seule la tâche en cours de traitement est marquée comme In-Progress, tandis que les autres restent disponibles.