[ECS Fargate] [request]: cache common Windows layers

### 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**
Currently ECS Fargate Windows caches the most recent base images ( https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-windows-behavior.html )

However, real world usage would always include a second layer, e.g. .net framework 4.x . As these layers approach ~3gb in size, it would be good to have these cached with the same lifecycle as the base image.

**Which service(s) is this request for?**
This could be Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We want to improve deployment times of Windows containers on Fargate.

**Are you currently working around this issue?**
We've optimized our own layers as well as we can, but a bare .net image just takes 8 minutes to start (vs ~3 for a base 2022core image)

Start with the linked ECS Fargate Windows behavior documentation and compare its current base-image caching lifecycle with the requested caching of common additional layers such as .NET Framework 4.x. The issue names no repository files or tests; done means the supported caching behavior is defined and Windows container deployment startup time is improved.

Written by the indexing model from the issue text.