Send only selected inputs on the pipeline schedule page

What does this MR do and why?

This MR updates the pipeline inputs selector functionality to send only selected inputs. This change doesn't affect the new pipeline page, where only modified inputs are sent.

With this change, only selected inputs are sent to the pipeline schedule, and unselected inputs that have previously saved values are removed from the schedule properties, letting these inputs use their default values.

References

• #534684 (closed)

Screenshots or screen recordings

Screen_Recording_2025-06-12_at_13.06.44

How to set up and validate locally

1. In the pipeline editor, create some inputs:

spec:
  inputs:
    environment:
      type: string
      description: "Target environment for deployment"
      options:
        - "development"
        - "staging"
        - "production"
      default: "development"
    worker_count:
      type: number
      description: "Number of worker processes to spawn"
      default: 2
    enable_debug:
      type: boolean
      description: "Enable verbose debug output"
      default: false
    version_tag:
      type: string
      description: "Version tag for the release (format: vX.Y.Z)"
      regex: "^v\\d+\\.\\d+\\.\\d+$"
      default: "v1.0.0"
    allowed_paths:
      type: array
      description: "Paths to include in processing"
      default:
        - "src/"
        - "lib/"

2. Navigate to Build -> Pipeline schedules -> New pipeline schedule and create a schedule selecting some inputs.
3. Save the schedule and verify the saved inputs are preselected when editing this schedule.
4. Update an input value and verify it gets stored for the schedule.
5. Unselect a saved input and verify it gets removed from the schedule.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #534684 (closed)