[EKS] [NEURON][request]: add support for k8 neuron scheduler extention

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
For the inferentia nodes it supports the k8s scheduler as described [here](https://awsdocs-neuron.readthedocs-hosted.com/en/latest/neuron-deploy/tutorials/k8s-neuron-scheduler.html). This currently is not supported in EKS and we want to add that support.

**Which service(s) is this request for?**
EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
When the POD is scheduled in the inferentia node there is a requirement to have contiguous neuron devices to be available to the container running in the POD. The neuron scheduler extension has added that support and without this if more than 1 devices is requested then non contiguous devices will be made available to container and the neuron runtime will fail.

**Are you currently working around this issue?**
No workaround

**Additional context**

**Attachments**

No repository files or tests are identified in the issue. Start with the linked AWS Neuron Kubernetes scheduler documentation and the EKS scope described here; clarify the integration requirements and validation needed for contiguous Neuron device allocation. Done should mean the requested scheduler support is available in EKS and the stated pod scheduling failure is addressed.

Written by the indexing model from the issue text.