Configuration pipeline form: automatically populate pipeline parameters from input config yaml parameter

[kamyshova]

Background
Implement a feature that automatically populates pipeline configuration parameters in the UI form when the inputs_yaml parameter is provided. If a user defines the inputs_yaml parameter, any parameters within the pipeline configuration that are also defined in the inputs_yaml should be auto-populated in the pipeline UI form.

Approach

• The UI pipeline form should automatically fill in parameters that exist both in the pipeline configuration and the inputs_yaml.
• If a parameter in the UI already has a value, it should be not overwritten by the value from inputs_yaml.
• If a parameter is not present in the inputs_yaml, it should retain its default value or user-provided input.
• If a parameter extracted from inputs_yaml is invalid or does not match the expected type in the UI form it would be great to provide appropriate validation error in the UI.
• If inputs_yaml contains parameters that are not recognized by the pipeline configuration, they should be ignored.
• It would be great to add visual indicators for parameters populated from the inputs_yaml so users can easily identify auto-filled fields.
• Users can change the auto-populated values if necessary, in which case the visual indicator is disabled.