The specific error message should have been validated on the CIDR ranges step and the cluster wouldn't have to fail to install.

This story should contain discussions on how this new CIDR and VPC subnet ranges validation can be implemented on the wizard step(s) and also some UX mockups on how it would look and behave. cc smordech-quota 

Design Doc: Validate machine and subnet CIDR range selection before cluster provisioning [PD-1574/1593]

This issue was raised in the OSD usability testings 

Relevant Links

https://docs.google.com/document/d/1JxUJJ92PhsXkxG8elfm34qFiyZifJ67blH6yyDKb53o/edit#heading=h.6zkv4fx7d4fc

https://redhat-internal.slack.com/archives/C01G3PL29SS/p1695391346895439

We will implement local validations on the CIDR fields of the CIDR ranges step in the ROSA Classic, Rosa Hosted and OSD AWS wizards.

Acceptance Criteria

1. Machine CIDR is validated to make sure it includes the starting IP for every selected subnet (private and public).
2. Service CIDR is validated to ensure no overlap with subnet CIDRs. (Service CIDR should not contain starting IP of any subnet, and subnet CIDRs should not contain starting IP of service CIDR)
3. Pod CIDR is validated to ensure no overlap with subnet CIDRs or service CIDR. (Pod CIDR should not contain starting IP of any subnet, and subnet CIDRs should not contain starting IP of pod CIDR. Pod CIDR should not contain starting IP of service CIDR, and service CIDR should not contain starting IP of pod CIDR.)
4. Validations should occur whether the user has entered values or used the defaults.