[backport v2.7.next1] Ability to deploy AWS external tree provider in RKE2

[github-actions]

This is a backport issue for #9110, automatically created via GitHub Actions workflow initiated by @gaktive

Original issue body:

Internal Ref: SURE-4760

The external AWS cloud provider (CCM) deploys onto a cluster and relies on the hostname and/or --provider-id flag (kubelet) to describe the node and initialise into the cluster.

With v2-provisioning, the hostname is always set to a node pool naming convention (OS (see userdata example below) & with -hostname-override), and there appears to be no way of providing the values dynamically to the -provider-id flag.

[slickwarren]

tested as part of regression tests in rancher, tracked in Qase. All tests are passing on 2.7.11-head