[BUG] Pipeline: next node doesn’t start when Interrupt After/Before is used

[epamLDadayan]

Title: Pipeline: next node doesn’t start when Interrupt After/Before is used

Description:
Across node types (LLM, Agent, Function, Loop, etc.), using Interrupt After on a preceding node or Interrupt Before on the target node prevents the pipeline from advancing. User input is captured, but the result isn’t emitted to the next node and execution stalls.

Steps to reproduce:

1. Create a pipeline with Node A -> Node B (any node types).
2. Case 1: Enable Interrupt After on Node A, run until it pauses, provide input, submit.
3. Case 2: Enable Interrupt Before on Node B, run the pipeline to reach Node B and provide the required input.

Actual Result:

• Pipeline remains on the interrupted node.
• Output/input is not emitted to the next node.
• Node B never starts; downstream nodes do not execute.

Expected Result:

• After submitting input on Interrupt After, Node A finalizes, emits its output, and pipeline advances to Node B.
• With Interrupt Before on Node B, Node B should initialize, accept input, execute, and then continue the flow.

Notes (optional):

• Reproducible with LLM, Agent, Function, Loop, Router/Decision/Condition nodes.
• Example pipeline: https://dev.elitea.ai/alita_ui/406/pipelines/all/3?viewMode=owner&name=BUG%20-%202111

[epamLDadayan]

Verified on DEV env

[epamLDadayan]

Verified on Stage env