[ECS] [request]: ECS Cloudformation Update Stack timeout

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

I would be able to have the stack timeout parameter in AWS CLI and Cloudformation

Example?

`create-stack` and `update-stack` had a `--timeout-in-minutes` option. Currently is only `create-stack`

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

This could be Fargate, ECS, Fargate

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

When updating a Cloudformation (ECS) Stack with a new Container Image, there is any way to control the timeout so if the service does not stabilize it rolls back automatically

The UpdatePolicy attribute which is part of the Auto Scaling Group does not help since instances are not being created.

The stack essentially just stays in the UPDATE_IN_PROGRESS state until it hits the default timeout (~3 hours), or you trigger a Cancel the update.

Start with the request's comparison of AWS CLI create-stack and update-stack, then review the CloudFormation update behavior described for ECS and Fargate. Done would mean an update-stack timeout parameter is available and a non-stabilizing service update can roll back automatically instead of waiting for the default timeout.

Written by the indexing model from the issue text.