[ECS Fargate] [request]: Fargate task patching frequency and improved patch release coordination.

### 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**

Provide more customer control over Fargate task patching frequency and improved patch release coordination.

**Which service(s) is this request for?**

AWS Fargate, Amazon ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

Customers are experiencing increased frequency of Fargate task patching retirements, with some services seeing patches approximately twice per month. For services managing persistent connections with IoT devices, each task retirement causes disruptions as it forces instance rotations, leading to connectivity loss and service interruptions.

**Are you currently working around this issue?**
Currently, customers can only control task replacement timing by manually initiating ECS service updates before the maintenance deadline.

**Additional context**

Customers have noted the patch frequency appears higher than historical patterns.
Multiple patch releases scheduled close together (e.g. one patch starting October 7 and another notification for October 17) create additional operational burden
Request ability to distinguish between critical security patches vs regular maintenance updates, similar to database services
Consider bundling rollouts that are scheduled close together to reduce operational impact
Need better coordination of patch releases to minimize customer impact while maintaining security compliance

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