Error logging being expanded for failed task triggers

When task runs or batch items fail to trigger, the system can sometimes fail without leaving enough context to diagnose the root cause. Detailed error logging is being added to the run engine and batch queue handlers to capture these missing details.

Engineers can now see exactly why a task run failed to enqueue or a batch item failed to trigger. The new logs capture critical metadata including environment IDs, task identifiers, batch item indexes, and attempt numbers. This removes the guesswork when diagnosing task failures in the core engine, allowing the team to trace exactly where and why a payload was dropped.