chore: v2 - sync behavior to validation fix resolution

[maxy-shpfy]

Description

The MissingPipelineInputValueResolution component has been updated to set a pipeline input's value directly rather than its default value. The effective value displayed and edited is now derived from input.value ?? input.defaultValue, prioritizing an explicitly set value over the default. The label and UI copy have been updated from "Default value" to "Value", and a "Use as default" indicator (with a checkbox icon) has been added to the label row to communicate intent to the user.

Screenshots (if applicable)

Test Instructions

1. Open a pipeline in the editor that has a missing pipeline input value issue.
2. Verify the resolution panel displays "Set a value for pipeline input" with a "Value" label and a "Use as default" indicator.
3. Enter a value and confirm it is saved as the input's value (not the default value).
4. Verify that if an explicit value already exists, it takes precedence over the default value in the text area.

Additional Comments

The ioActions.setInputValue call replaces the previous ioActions.setInputDefaultValue call, so any downstream handling of input values vs. default values should be verified to ensure compatibility.

[github-actions]

🎩 Preview

A preview build has been created at: 07-29-chore_v2_-_sync_behavior_to_validation_fix_resolution/24818e4

[maxy-shpfy]

• refactor: remove setinputdefaultvalue as obsolete from actions #2591
• chore: v2 - sync behavior to validation fix resolution #2590 👈 (View in Graphite)
• fix: v2 - support value and default in input nodes #2589
• master

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

[maxy-shpfy]

Merge activity

• Jul 30, 5:10 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 30, 5:18 PM UTC: Graphite rebased this pull request as part of a merge.
• Jul 30, 5:22 PM UTC: @maxy-shpfy merged this pull request with Graphite.