[AAP-82758] Keep Add step and link sequential in Workflow Visualizer

[lgalis]

Summary

• Fixes Workflow Visualizer Add step and link saving the new node as a parallel root sibling instead of a sequential child of the selected node.
• Stop associating labels, instance groups, and credentials unless the job template has Prompt on Launch for those fields, so save no longer fails with Field is not configured to prompt on launch after the node is already created.
• Sanitize unprompted related fields when adding a new node, and re-mark the source node after fromModel so the parent-child edge is persisted.

Type of Change

• Bug fix
• Enhancement
• Tests
• Documentation
• Other (please specify)

Risk Analysis - REQUIRED

• High — Broad platform impact (e.g., SWR config, shared framework components, authentication, routing, API wrappers, build/bundler config). Changes affect multiple workspaces or could cause widespread regressions.
• Medium — Scoped but cross-cutting (e.g., shared utility functions, changes to multiple pages within one workspace, component library updates, test infrastructure). Limited blast radius but touches common code paths.
• Low — Narrowly scoped (e.g., single page fix, styling tweak, documentation, test-only changes, copy/string updates). Minimal risk of unintended side effects.

Testing

Ephemeral E2E Tests

Once PR is ready and preliminary checks pass, trigger tests by posting a comment /run-playwright on this PR.

Tests run against a fresh AAP instance (version based on branch).

Manual Testing

1. Create a Workflow Job Template and add a Job Template as the first node; save.
2. Create another Job Template that has Labels assigned but Prompt on Launch for Labels disabled (other prompted fields are fine).
3. Open the workflow in the Workflow Visualizer.
4. On the first node, choose Add step and link, select the second Job Template, finish, and save.
5. Confirm save succeeds with no Field is not configured to prompt on launch error.
6. Confirm the new node is a sequential child of the selected node, not a parallel sibling under Start.
7. Repeat with an approval node linked after an existing node.

Unit Tests

• useSaveVisualizer.test.ts — does not associate unprompted related resources; associates a new node as a sequential child of the source node.
• buildEffectivePrompt.test.ts — clears unprompted related fields for new nodes; preserves prompted fields.

Made with Cursor

[github-actions]

@lgalis — SonarQube Quality Gate failed:

• Coverage on New Code: 46.2%

Please address the SonarQube findings.

[sonarqubecloud]

Quality Gate failed

Failed conditions
46.2% Coverage on New Code (required ≥ 90%)

See analysis details on SonarQube Cloud