[Bridge] Folded Nexus operation progress onto the next Workflow Task.

[moetemp]

What changed?

This PR folds Nexus operation progress onto the caller's next Workflow Task scheduled event, as one more kind of carried state on Jetty's Workflow Task hook (moetemp/temporal#55).

• nexusProgressCarrier joins taskCarriers. The hook's rules apply: one follow-up task, no progress on a heartbeat task or its retry, the failover hold.
• The Workflow keeps a TaskCarriedIndex keyed by scheduled event ID. The event lists progress by scheduled event ID, not by key order.
• nexusoperation.progressMinInterval (1 s) rate-limits tasks that progress schedules.
• A passive cluster forwards deliveries to the active one.

It replaces the Bridge half of moetemp/temporal#39. The hook, the heartbeat hold and the failover hold now live in Jetty.

Why?

Progress rides the scheduled event (DD-34), and a burst costs at most one extra task (DD-55). SDKs replay a heartbeat chain differently from live, so progress there could land in another activation (DD-52).

How did you test it?

Link to a test plan if any -

• Unit Tests
• Staging
• End to End Tests

Functional TestNexusOperationProgress* on both caller kinds, TestNexusProgressAcrossFailoverConversion, and the xdc TestNexusProgressForwardingSuite.