Remove edge conflict logic from delete workflow node

[mabashian]

ISSUE TYPE

• Feature Task

COMPONENT NAME

• UI

SUMMARY

link #2255

This issue tracks the UI work needed to support #2255. When a user deletes a workflow node, we roll the rest of the branch back into the vacated spot left by the deleted node. When this happens, there's a chance that sibling edge types could break our rule of mixing always and success/failure edge types.

Example, if we delete this node:

Then we now have sibling nodes (one with always and one with success). This currently results in what we refer to as an edge conflict:

#2255 removes this restriction so the UI can remove the notion of an edge conflict. In the above example, after deleting the node there should be no "edge conflict" indicators and the save button should be enabled.

Acceptance Criteria:

1. As a user, I can delete a node with the WF visualizer without causing an edge conflict so I can create manageable workflows
2. Tests pass (e2e)
   • A test should be written that confirms that deleting a node does not result in an edge conflict and the user can edit the new child node and select any of S/F/A