[EKS] [request]: Release LivePatch enabled AL2 EKS AMI

### 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**
Release Livepatch enabled AL2 EKS AMI

**Which service(s) is this request for?**
This could be ECS, EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Various industry compliance line SOC2 mandates to patch the OS at least once a month and this is difficult for EKS nodes as patching requires machine reboot which is not feasible with EKS nodes.

**Are you currently working around this issue?**
With every EKS version release right now, we need to manually create a new AMI with livepatch installed. Also, this process of installing livepatch does not work on GPU/Neuron enabled AMI as pods unable to detect the GPU/Neuron device if we do so.

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

No repository files, tests, or implementation entry points are identified. Start by clarifying the supported EKS AMI variants and Livepatch requirements with maintainers, including GPU and Neuron compatibility. Done would be an officially released Livepatch-enabled AL2 EKS AMI that addresses the stated compliance need.

Written by the indexing model from the issue text.