Fix removing array type values in machine pool configs

[momesgin]

Summary

Fixes #10693

In rke2.vue, before saving the new changes made to the machine pools configuration we run syncMachineConfigWithLatest function, it gets the latest(last saved) config from the BE, then uses Lodash merge function to update it with the current changes made by the user. The problem is that if the user removes an item from an array type config value(e.g. network in vSphere), it will never work due to the default behaviour of Lodash merge function. Example:

const lastSavedConfigFromBE = { a: ["test"] };
const currentConfigByUser = { a: [] };

merge(lastSavedConfigFromBE, currentConfigByUser) // { a: ["test"] }

A new helper function customMerge is created to address the issue by correctly replacing the old array values with the new values during the merge process.

Areas or cases that should be tested

This change is not limited to vSphere's machine pool config, any array type values for any provider's machine pool config will be affected. I haven't found any examples so far, but I believe the removing issue exists for any provider's array type value in their machine pool config, and this PR should fix them too.

Areas which could experience regressions

Same as above.

Screenshot/Video

Screen.Recording.2024-04-02.at.1.26.27.PM.mov

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

[codyrancher]

I have a feeling that we're going to want to change the functionality of syncMachineConfigWithLatest and just replace the metadata instead of merging.

With that said, let's see how this works in practice.

[richard-cox]

I'm not sure of the possible usages outside of shell/edit/provisioning.cattle.io.cluster, can this live there and be titled something like poolConfigMerge?

Otherwise it probably needs to be generic and go into utils/object

[richard-cox]

I haven't validated by vsphere creds yet, but general edit of non-vsphere looks good. If you've validated the issue is resolved then lets get this in.

[momesgin]

I haven't validated by vsphere creds yet, but general edit of non-vsphere looks good. If you've validated the issue is resolved then lets get this in.

I just tested it and it works as expected