[Feature Request] Utility to detect when deadlock detector triggers

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

Users would like the ability to programmatically detect when the deadlock detector has triggered (and caused the workflow task to fail), so they can instruct their code to stop processing. This would be used to write defensive logic to prevent zombie threads or loops from running after the workflow task has failed. This typically happens when there’s a bug in user code, such as a spinning loop that runs indefinitely.

Describe the solution you'd like

Currently, the SDK throws a DestroyWorkflowThreadError when a workflow API (e.g., sleep, scheduleActivity) is used after the deadlock detector has been triggered.

It would be great to have a method similar to Thread.currentThread().isInterrupted() that returns true (or an exception). This would allow developers to break out of loops or take alternate actions.

Additional context

Start by tracing the deadlock detector path and the existing DestroyWorkflowThreadError behavior when workflow APIs such as sleep or scheduleActivity are called. Define how a workflow can observe the detector before making those calls, and verify that the signal lets defensive loops stop after the workflow task fails.