feat: clone pipeline from run with arguments

[maxy-shpfy]

Description

Closes https://github.com/Shopify/oasis-frontend/issues/411

Updated behavior for "Clone Pipeline" button on the Pipeline Run Details page. This button clones a pipeline while preserving the arguments used in the original run, allowing users to quickly create a new pipeline with the same parameter values.

Following decisions made in sync meeting:

Where to hold arguments
In short-term it’s OK to store them anywhere as long as this implementation detail does not leak into submitted and exported pipelines.
Currently, UI code stores pipeline-level arguments inside pipeline-level inputs (InputSpec.value).

To keep behavior consistent former "Clone Pipeline" button should be removed - https://app.graphite.com/github/pr/TangleML/tangle-ui/1628/fix-remove-redundant-clone-pipeline-from-the-top-menu

Type of Change

• New feature
• Improvement

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Test Instructions

Screen Recording 2026-01-13 at 10.39.45 PM.mov (uploaded via Graphite)

1. Navigate to a completed pipeline run
2. Verify that both clone buttons are visible:
   • The original "Clone Pipeline" button
   • The new "Clone Pipeline with Arguments" button
3. Click the "Clone Pipeline with Arguments" button
4. Verify that the new pipeline opens in the editor with all input parameters pre-filled with values from the original run argumentsFol

[maxy-shpfy]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat: clone pipeline from run with arguments #1624 👈 (View in Graphite)
• feat: copy submit pipeline arguments from custom run id #1623
• feat: copy submit run arguments from recent run #1622
• feat: submit run with arguments #1618
• fix: call rerun pipeline with actual task arguments #1615
• feat: display arguments values in input nodes in run view #1612
• feat: display taskspec arguments values in run view #1611
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[camielvs]

Thinking out loud: does it need to be a separate button?

The clone button could clone the original pipeline and then separately clone the overrides/run arguments. Then you get the pipeline (with its original input nodes & defaults) with the configured arguments as it was at time of submission. The user can then choose, via the dialog, to reconfigure and submit with those arguments or submit the original as per existing flow for a new pipeline

[maxy-shpfy]

@camielvs I removed additional button and modified the behavior of existing "Clone pipeline" button

[camielvs]

LGTM