Bug 1997419

Description of problem:
When the user makes changes to a BuildConfig (or Pod) with the environment page or tab the form should disable the save button when the form is not filled out correctly.

For example if the user fills our a value without a name.

Prerequisites (if any, like setup, operators/versions):
None

Steps to Reproduce
Open developer perspective and navigate to Builds
Click "Create BuildConfig" button
Create the BuildConfig without additional changes
Switch to the "Environment" tab
Enter an value without a name and press save.
Actual results:
The name field is not marked as required.
The save button is clickable, the form was submitted to the backend and then shows an error like this:
Error "Required value" for field "spec.strategy.sourceStrategy.env[0].name".
Expected results:
The name column should be marked as required with a red asterisk.
The save button should be disabled as long as the form is invalid. The fields which are invalid should show an error so that the user can understand which field is required.
Reproducibility (Always/Intermittent/Only Once):
Always

Build Details:
4.9

Additional info:
This is an follow up on ODC-6206 which changed this behavior. Issue was mentioned by Abhinandan Das

Earlier fields without a name was just dropped. The new version doesn't drop the inserted user data and shows this error.