Add logs for stall detection

[amankrx]

Description

Added some logs for detecting stalls if any and what caused those stalls.

Fixes # (issue)

Type of change

Please delete options that aren't relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to
  not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please also list any relevant details for your test configuration

Checklist

• Updated documentation if needed
• Tests added/amended
• bazel test //... passes locally
• PR is contained in a single commit, using git amend see some docs

---

This change is 

[MarcusSorealheis]

High‑volume logs on hot paths can worsen stalls. Please ensure new logs are rate‑limited or include stable identifiers (action_id, worker_id, invocation_id, queue name) so stalls can be correlated across scheduler/worker/store. Basically, log state transitions.

[amankrx]

High‑volume logs on hot paths can worsen stalls. Please ensure new logs are rate‑limited or include stable identifiers (action_id, worker_id, invocation_id, queue name) so stalls can be correlated across scheduler/worker/store. Basically, log state transitions.

That's why I have added the log level as trace. We won't be using the trace log level in production. These logs are just added in case we experience stalling with normal deployment and we would like to find the source of the stall.