vSphere - Adding a second or subsequent pool in Edit mode does not populate default values and shows Error banner wrongfully

[momesgin]

Setup

• Rancher version: 2.9-head, 2.7-head(no error banner though, since it was implemented in 2.8)
• Rancher UI Extensions:
• Browser type & version:

Describe the bug

Adding a second or subsequent pool in Edit mode does not populate default values for either specific vSphere fields(e.g. Datacenter, DataStore, etc) or other generic configuration fields(e.g. CPU , Disk ,etc). This also leads to display error banners wrongfully for the new pool.

To Reproduce Create a vSphere cluster, save it and then go to Edit Config and add a new pool

Result Does not populate default values and displays error banner for the new pool

Expected Result Should populate default values and should not display error banner for the new pool

Screenshots

https://github.com/rancher/dashboard/assets/135728925/d9b98522-9fd6-4d5b-bec8-e10476ccaff2

[momesgin]

/backport v2.8.next1

[aalves08]

Added automation-candidate based on the fact that we have a pattern to mock a cluster, like https://github.com/rancher/dashboard/blob/master/cypress/e2e/blueprints/nav/fake-cluster.ts... will take a bit of time to get all of Vsphere responses mocked, but seems doable imho

[IsaSih]

Tests pass on v2.9-81337b95660cba868629d6fe769bd7e8242b5aee-head