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.

从 MergerService/Runners/MainRunner.cs 开始，重点查看第 36-40 行，并通过运行至少两个类型不同的 ingestion job（例如 swap、new 和 update）来复现该问题。跟踪存在多个 task 时哪些 task 被标记为 In-Progress。完成的标准是：只有正在处理的 task 被标记为 In-Progress，其他 task 保持可用。