[EKS] [request]: Image streaming

### 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**
Could EKS provide something analogous to GKE's image streaming capability?
https://cloud.google.com/kubernetes-engine/docs/how-to/image-streaming

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
It's pretty common for some workloads (..data science) to depend on images that are quite large. These workloads are often batch in nature and often require a lot of compute, so to keep the costs down it's a common practice to scale to 0 (e.g. with Karpenter). That however means that for a sufficiently large workload, we're almost always running on a fresh node and the workload has to sit a long time (10+ minutes) in initialization while the images are being pulled, which can become a hard blocker for running such use-cases on Kubernetes/EKS in the first place.

**Are you currently working around this issue?**
Outside of using GKE, theoritically this could be optimized by baking images into custom AMIs. I'm not sure how well that could work given the high rate of changes that we often see on given images.

Start by reading the linked GKE image streaming documentation and compare its capability with the EKS and ECR services named in the issue. Done would require a defined, supported EKS/ECR approach that reduces fresh-node startup time for large images, but the issue does not identify repository files or tests.

Written by the indexing model from the issue text.