Description of problem:

Cluster wizard submission fails with inline error due to previously selected security group references. For example, user has initially selected a VPC and security groups from VPC settings but in-between user went back and proceeded the wizard flow without custom VPC.
During cluster creation, cluster submission has failed with inline error. It looks the security group definition submitted from UI to backend create issues. We should avoid this from UI.

How reproducible:

always

Steps to Reproduce:

1. Open OCM UI staging.
2. Open an OSD wizard.
3. Choose Infrastructure type as CCS and choose cloud provider as AWS.
4. Proceed further steps and reach to "Networking" step.
5. Select the "Install into an existing VPC" option.
6. Click "Next" button.
7. Select a VPC (make sure VPC has some security groups configured).
8. Under "Advanced security group" section, select few security groups.
9. Click "Back" button.
10. Deselect "Install into an existing VPC" option.
11. Click "Next" button.
12. Proceed further steps and reach to "Review and create" step.
13. Click "Create cluster" button.
14. See the behavior.

Actual results:

At Step 13, Cluster wizard submission reported a failure as we try to submit security group definition for non BYO-VPC cluster. This could be due to security group references wrongly picked up from Step 8 even after changing the flow.

Expected results:

Cluster submission should be successful and no security definition should be added submitted and configured in above situation.