[BUG]: Prevent Editing or Deleting Nodes While Workflow Is Running

[amaan1114]

Bug Summary

Users can currently edit node configurations or delete nodes while a workflow is actively executing. This can lead to inconsistent execution behavior and unexpected results.

---

Current Behavior

While a workflow is running, users are still able to:

• Edit node configurations.
• Delete existing nodes.
• Modify the workflow structure.

These changes can occur while the execution engine is processing the workflow, potentially causing inconsistencies between the execution state and the workflow definition.

---

Expected Behavior

Once a workflow execution starts, the workflow should become read-only until execution completes.

During execution:

• Node configuration should not be editable.
• Nodes should not be deletable.
• New nodes should not be added.
• Connections between nodes should not be modified.

If a user attempts to perform any of these actions, the application should display an appropriate message such as:

"This workflow is currently running. Stop the execution before making changes."

Normal editing should be restored once the workflow reaches a terminal state (Success, Failed, or Cancelled).

---

Steps to Reproduce

1. Open a workflow in the workflow builder.

2. Start a workflow execution.

3. While the workflow is still running, attempt to:

   • Edit a node configuration.
   • Delete a node.
   • Modify the workflow graph.

4. Observe that the changes are currently allowed.

---

Additional Context

• The workflow builder should enter a read-only state during active execution.
• This restriction should apply only to the workflow currently being executed.
• User feedback should clearly explain why editing is temporarily disabled.
• This helps maintain execution consistency and prevents accidental modifications during runtime.