Correct volume limits for m6id and x2idn instance types

[talnevo]

Is this a bug fix or adding new feature?
This is a bug fix

What is this PR about? / Why do we need it?
This PR adds support for m6id and x2idn instance types to volume_limits.go so that the Kubernetes scheduler will be able to correctly determine the number of volumes available on these node types.
This PR also removes the x2idn instance types from the non Nitro list.

What testing is done?
No direct testing was performed: Kubernetes tests on nodes based on m6id.12xlarge, m6id.16xlarge, m6id.32xlarge, x2idn.16xlarge & x2idn.32xlarge instance types have shown that there is a gap between the number of [volume requiring] pods the Kubernetes scheduler allows to run on a node and the number of pods that are able to attach their respective volume.
Our research brought us to determine that this is the place to make the change that will fix this problem.
A similar issue was observed last year with nodes based on m5d.16xlarge & m5d.24xlarge. This older issue no longer exists. We concluded that a change to volume_limits.go introduced in March 2022 fixed the problem for m5d instance types and we want to do the same for m6id and x2ind based nodes.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: talnevo (f509ab6, 8df4671)

[k8s-ci-robot]

Welcome @talnevo!

It looks like this is your first PR to kubernetes-sigs/aws-ebs-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/aws-ebs-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @talnevo. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sunir1]

LGTM

[ConnorJC3]

/ok-to-test

[ConnorJC3]

/lgtm
squashed to 1 commit

[torredil]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sunir1, torredil

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [torredil]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment