[backport v2.9.3] Node Drivers incorrectly supply addCloudCredential, resulting in missed Cloud Credential pages

[github-actions]

This is a backport issue for #11974, automatically created via GitHub Actions workflow initiated by @richard-cox

Original issue body:

SURE-9062

Setup

• Rancher version: 2.9.0

Describe the bug

• Before CloudCredential is not created when using a custom Docker Machine Driver. #7023 we would block the user from creating a cloud cred via list, but always request one when creating via the prompt before the create cluster flow
• Following that we now honour management.cattle.io.nodedrivers spec.addCloudCredential of false, so if set we won't allow the user to create one of that type at all
• addCloudCredential for all pre-supplied node drivers comes from https://github.com/rancher/rancher/blob/7bd6951a7d07f8b00b61811fd89cc673319f85b4/pkg/data/management/machinedriver_data.go#L140. A lot of these are set to false
• At least nutanix needs it to be true, possible a lot of others too
• We need to confirm who owns that file / those lines and request the correct values are set

To Reproduce

• Enable Nutanix driver
• Attempt to create an RKE2 nutanix cluster

Result

• no prompt to create / select cloud creds

Expected Result

• prompt to create / select cloud cred