[feature]: add goroutine IDs to logs for sections where we use worker pools

Is your feature request related to a problem? Please describe.

We use worker pools in a few spots, via fn.ParSlice or other means. The logs do not indicate which goroutine generated which logs, which makes finding the root cause for an issue more difficult.

Describe the solution you'd like

If we generate a unique ID for each goroutine before entering these parallel sections, and add it the logs, that would aid debugging. We could probably reuse the logic for the tapd daemon runtime ID.

Describe alternatives you've considered

Counting log lines manually.

Additional context

Start by locating the worker-pool sections that use fn.ParSlice or other parallel mechanisms, then inspect the tapd daemon runtime ID logic for possible reuse. The work is complete when logs from those parallel sections include a unique goroutine ID and the affected logging remains useful for tracing failures.