MID-11186 Fix worker progress reporting

[kay1313]

Summary

Fixed progress reporting for worker subtasks in distributed bucketed activity tasks.

Previously, worker rows in the subtasks table used progress derived from the root/coordinator activity. As a result, all worker rows could display the same aggregate progress as the parent task.

The fix keeps the existing root-task progress path for non-worker subtasks, but for bucket-processing worker subtasks it uses the matching per-worker item progress from the parent activity state overview. This lets the GUI display worker-local processed object counts instead of coordinator aggregate progress.

Also added support for converting worker task overview item counters into ItemsProgressInformation.

Details

• Worker subtasks are detected using BucketsProcessingRoleType.WORKER.
• Worker progress is matched by worker task OID in activityState.tree.activity.task[].
• Worker rows use item/object counters, not bucket counters.
• Non-worker subtasks continue using the original root-task progress lookup.
• Leaf activity progress with direct item progress is handled by getProgress(), so count-only worker progress does not produce a fake progress bar.
• Added a regression test proving worker rows use worker-local item progress and do not use root bucket progress.

Testing

Added TestTaskInformation.testWorkerProgressUsesWorkerItemOverview.

The test verifies that:

• root/coordinator bucket progress is present,
• worker rows display worker-local item counts,
• bucket progress is not synthesized for workers,
• progress bar value is -1 when no expected total is available,
• worker overview entries are matched by worker OID.