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.

Inizia da MergerService/Runners/MainRunner.cs, in particolare dalle righe 36-40, e riproduci il problema eseguendo almeno due job di ingestione con tipi diversi, come swap, new e update. Traccia quali task vengono contrassegnati come In-Progress quando sono presenti più task. Il lavoro è completato quando solo il task in fase di elaborazione è contrassegnato come In-Progress, mentre gli altri rimangono disponibili.