Bug 1986631

Description of problem:
When the user makes changes to a BuildConfig (or Pod) with the environment page or tab this could result in different errors:

Usability error: When the user doesn't enter a name this entries are just dropped when the form is saved.

Crash: When the user enters a name but do not enter a ConfigMap or Secret value the form crashs after saving. (The data are saved and the form will crash now when the user opens the tab.)


Version-Release number of selected component (if applicable):
4.9

How reproducible:
Always

Steps to Reproduce the usability error:
1. Open developer perspective
2. Navigate to Builds
3. Click on "Create BuildConfig" button
4. Just create the BuildConfig without additional changes
5. Switch to the "Environment" tab
6. Press "Add variable" or "Add from ConfigMap or Secret", enter an value or select a resource WITHOUT adding a name
7. Press "Save" (environment variable without a name is just dropped)

Steps to Reproduce the crash:
1. Open developer perspective
2. Navigate to Builds
3. Click on "Create BuildConfig" button
4. Just create the BuildConfig without additional changes
5. Switch to the "Environment" tab
6. Press "Add from ConfigMap or Secret", add a name but DO NOT selecting a ConfigMap or Secret
7. Press "Save"

Actual results:
1. Usability error: Environment variables without a name are just dropped
2. Crash: Crash 

Expected results:
1. Usability error: The name should be marked as required. The form should disable the create button when a value is entered or selected without a name.
2. Crash: No crash 

Additional info:
None