[EKS]: Add support for running WASM containers on EKS using WASI

### 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**
- Add support for running WASM containers on EKS using the webassembly interface (WASI)

**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?**
- WASM containers are smaller, faster (launching), and more secure than traditional Linux containers. Because of their smaller and more compact form, they can enable interesting use cases such as running workloads at the edge or in resource constrained environments as well as for workloads that need to scale very quickly in a short amount of time. Some example workloads that would benefit include:
- Real time bidding platforms (ads, trading platforms, etc.) that are latency sensitive - typically running close to their workloads on something like Outposts and/or Local Zones
- ?

**Are you currently working around this issue?**
- Currently investigating https://www.fermyon.com/spin

**Additional context**
- containerd now supports running WASM containers via WASI https://github.com/containerd/runwasi using shims
- I am curious to hear from others in the community in terms of what they are looking to do with WASM (what type of workloads, motivations, deployment models today, etc.)

**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.)

The request concerns running WASM containers on EKS through containerd's runwasi shims, with Fermyon Spin noted as a current investigation. Start by reviewing the linked runwasi and Spin projects and the EKS deployment model. No repository files or tests are identified; done would require a defined supported integration and deployment scope.

Written by the indexing model from the issue text.