Issue #3605375: Add Clone node and Clone flow buttons to the orchestra_cm editor

Frank Mablyrequested to merge
issue/orchestra-3605375:3605375-add-clone-node into 1.x

Adds a Clone button beside Remove for both nodes and flows in the orchestra_cm (classic) editor.

  • Clone node (every node, the start included): duplicates the node with all of its current configuration (type, label, settings, routing and feature editors) under a fresh unique machine name and a "(copy)" label, and opens it. The clone is left unwired (no flow is copied), so its machine name stays editable for an immediate rename, like a newly added node.
  • Clone flow (beside Remove flow): duplicates the flow (same endpoints, condition plugin and condition input) under a fresh id, as a starting point for a sibling branch. Offered only on a flow that has a condition: a second always-taken edge between the same two nodes is a duplicate that could never behave differently, so the button is disabled without one and the handler refuses it too.

Both act on the live, even unsaved, edits, so the duplicate reflects what is on screen.

Tests

Kernel coverage for both handlers (OrchestraCmFormTest): a node clone copies type, label, feature state and settings input under a new key and leaves the source untouched; a flow clone is a no-op without a condition and duplicates a conditioned flow under a fresh id. All OrchestraCmFormTest tests pass, phpcs and cspell clean.

Merge request reports