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.

Comienza con MergerService/Runners/MainRunner.cs, especialmente con las líneas 36-40, y reproduce el problema ejecutando al menos dos trabajos de ingesta con tipos diferentes, como swap, new y update. Rastrea qué tareas se marcan como In-Progress cuando existen varias tareas. Se considera terminado cuando solo la tarea que se está procesando está marcada como In-Progress y las demás siguen disponibles.