As part of the changes for OCM-4917 , we now support setting ingress visibility independently from API privacy on cluster creation, rather than having to create the cluster and patch the ingress to public/private later. Because of these changes, we want to allow users to set ingress listening on cluster creation through the UI.

With the change being made to the CS API to support setting API and Ingress visibility independently upon cluster creation, the UI should add options for setting API and Ingress visibility to public or private after the user chooses a private cluster. There can be another UI option under the private cluster selection for selecting private/public ingress.

To set the ingress listening value on cluster creation, the `ingresses[0].listening` field in the API payload must be set to internal/external. The `api.listening` field will retain the value for private/public API, which is how it currently works.