[EKS] [eks-node-monitoring-agent] [request]: Support repair or cordon of nodes on IPv4 address exhaustion

### 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**
Support repair or cordon of nodes on IPv4 address exhaustion

**Which service(s) is this request for?**
EKS - `eks-node-monitoring-agent`

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
When a node monitored with `eks-node-monitoring-agent` has exhausted all available IPv4 addresses (e.g. due to ENI limitation), it may receive the `IPAMDNoIPs` or `ContainerRuntimeFailed`, neither of which trigger remedial action.

It would be useful for `eks-node-monitoring-agent` to support overriding the criticality of certain node health issues, or alternatively a solution which would cordon a node once it has exhausted all available IPv4 addresses.

**Are you currently working around this issue?**
N/A

**Additional context**
Used with aws-vpc-cni

**Attachments**
N/A

Start with the eks-node-monitoring-agent behavior described in the issue and review how it handles IPAMDNoIPs and ContainerRuntimeFailed. Determine whether the intended outcome is configurable issue criticality or cordoning/repair on IPv4 exhaustion; the work is done when the selected behavior is supported for nodes using aws-vpc-cni.

Written by the indexing model from the issue text.