Pass deployment state and version state in forceCAN signals

[Shivs11]

What changed?

• WISOTT

Why?

• Operational readiness. There could be a world where we want to "reset" a user's workflow state given that these workflows CAN so frequently.

How did you test it?

• built
• run locally and tested manually
• covered by existing tests
• added new unit test(s)
• added new functional test(s)

Potential risks

• None

---

Note

Introduces optional state override when force-continuing-as-new.

• New proto messages ForceCANDeploymentSignalArgs and ForceCANVersionSignalArgs with override_state fields; generated helper/pb code updated
• Deployment and Version workflows now receive forceCAN signals with args and, if provided, apply override_state before continue-as-new
• Added tests verifying override is honored (e.g., manager identity and metadata) after continue-as-new

^{Written by Cursor Bugbot for commit 1fd847d. This will update automatically on new commits. Configure here.}