Description of problem:

The vSphere plugin that allows users to configure the vsphere connection details handles some of the configuration properties incorrectly.

How reproducible:

100%    

Steps to Reproduce:

    1. Create a OCP 4.19 cluster using Cluster Bot (launch 4.19 vsphere)
    2. When the cluster is ready, open the vsphere connections modal.
    3. Notice that the vCenter cluster displays the value of the infrastructure CRD  network (spec.platformSpec.vsphere.failureDomains[0].topology.networks[0], for example "ci-vlan-918-7") rather than the vCenter cluster (example: "cicluster-3").
    4. Notice that the infrastructure CRD has an initial "resourcePool" attribute  (spec.platformSpec.vsphere.failureDomains[0].topology.resourcePool) similar to "/cidatacenter/host/cicluster/Resources/ipi-ci-clusters", and that there is no "folder" attribute (spec.platformSpec.vsphere.failureDomains[0].topology.folder).
    5. Make changes to the settings
    

Actual results:

• The "vCenterCluster" is initially populated incorrectly with the value from the first network.
• The "network" property in the Infrastructure CRD would be incorrectly overwritten with the value specified in the form for the vCenterCluster.
• The infrastructure CRD "resourcePool" attribute is overwritten to the format "/<datacenter>/host/<vCenterCluster>/Resources" and the /ipi-ci-clusters part is lost.

Expected results:

• The network in the Infrastructure CRD (`spec.platformSpec.vsphere.failureDomains[0].topology.networks[0]`) receives the value specified by the user in the new "Primary network" field
• The folder in the Infrastructure CRD (`spec.platformSpec.vsphere.failureDomains[0].topology.folder`) is updated with  the value the user specified in the "Virtual machine folder" field
• The resourcePool in the Infrastructure CRD (`spec.platformSpec.vsphere.failureDomains[0].topology.resourcePool`) is updated with the value "/<datacenter>/host/<vCenterCluster>/Resources". The extra segment "ipi-ci-clusters" is preserved 

Additional info:
The fix should be tested with a cluster that upgraded from OpenShift 4.17. In this version, the "cloud-provider-config" ConfigMap has a different format as an "INI" file rather than YAML.
In such a cluster, the UI (before the fixes) is unable to make any changes to the vsphere settings, and an error related to the "folder" and the "resourcepool-path" will appear when the user attempts to make any modification.
After the fix, the UI should be able to make all changes as for the OCP 4.19 version explained above.

 Please try to verify this bug with other setups that the Cluster Bot.