fix(ui): stabilize workflow node execution state updates

[JPPhoto]

Summary

Fixes workflow node execution state updates in the frontend event layer.

This change fixes nodes getting stuck in IN_PROGRESS or showing duplicate outputs when socket events arrive out of order or are repeated. The fix moves the event-ordering logic into shared helpers and uses a listener-local completed-invocation key set so late invocation_started / invocation_progress events cannot overwrite a completed node state.

Related Issues / Discussions

QA Instructions

1. On main, run a workflow in the Workflow Editor and examine the Outputs pane for a node that executes. You should see two outputs even when the node is executed once.
2. After pulling and building (or running in dev mode), open the Workflow Editor and run a workflow with visible node progress.
   • Confirm nodes transition from pending to in progress to completed.
   • Confirm completed nodes do not revert back to in progress during or after the run.
   • Confirm the Outputs pane does not show duplicate outputs for a single node execution.
3. Execute pnpm vitest run to run regression tests.

Merge Plan

Checklist

• The PR has a short but descriptive title, suitable for a changelog
• Tests added / updated (if applicable)
• ❗Changes to a redux slice have a corresponding migration
• Documentation added / updated (if applicable)
• Updated What's New copy (if doing a release after this PR)