Skip replication updates for deleted-workflow orphan runs

[jiechenz]

What changed?

On the passive replication-apply path, dispatchForExistingWorkflow now treats a closed target run with no current execution record (currentRunID == "") as a deleted-workflow no-op.

Why?

A reset/continue-as-new + delete the current run can leave the old closed run as orphan, this is true on passive side as workflow deletion will replicate to passive as well.

Then a force-replication SyncWorkflowState task on that orphan will hit currentRunId == "" and results in "unable to locate current workflow during update" error.

This fix skip the SyncWorkflowState when orphan is in post-deletion state.

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

• If a closed run legitimately should have a current record but it's missing due to a different bug, this now silently skips (logged) rather than surfacing — masking that class of inconsistency for closed runs