🌱 Add Arm support for EKS NodeGroup

[furkatgofurov7]

What this PR does / why we need it:
Adds support for ARM node groups. The new API field Arm was introduced in the NG properties and disabled by default, and when it is set to true with the appropriate instanceType (i.e a1.large instead of t3.medium) for ARM, a node group will be created based off of the ARM AMI types.

Which issue(s) this PR fixes
Issue rancher/dashboard#11629

Special notes for your reviewer:

To be able to use this feature:

1. A new operator release needs to be cut
2. A new release of the operator bumped in Rancher with a new field added in https://github.com/rancher/rancher/tree/release/v2.9/pkg/controllers/management/eks/test files
3. daily e2e tests might fail until then both of the above are completed

I have tested it by:

1. Releasing a new operator version from my fork
2. Bumping Rancher to the above version and building a local container image pushed to the registry (DockerHub in this specific case)
3. Upgrading the rancher to use the locally built rancher image right after it is installed in e2e tests

helm upgrade rancher rancher-stable/rancher --namespace cattle-system --set bootstrapPassword=admin --set replicas=1 --set hostname=rancher.my.org --set rancherImage="registry/target-repo" --set rancherImageTag="imageTag"

4. Check one of the nodegroups (ng1) created using the AL2_ARM_64 AMIType and a1.large instanceType while the other nodegroup (nodenametest) with AL2_x86_64 AMIType and t3.medium instanceType.

Checklist:

• squashed commits into logical changes
• includes documentation
• adds unit tests
• adds or updates e2e tests
• backport needed

[salasberryfin]

LGTM

[mjura]

@furkatgofurov7 please backport to release-v2.9