[ECS] [request]: CodeDeploy ECS Deploy stage times-out waiting for ECS Service to reach steady state.

### 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**
What do you want us to build?

If the Service is able to place maximum tasks in "Running" state, it should send an event message pointing out that most majority tasks are RUNNING, so that the Codepipeline "Deploy" stage does not time out.

**Which service(s) is this request for?**
This could be Fargate, ECS, EKS, ECR

ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

Codepipeline "Deploy" stage times out and fails waiting on the ECS service to reach "Steady State". This is a false positive as the ECS Service has started majority Desired Count for the tasks. However, some tasks are in pending. The ECS Service may not attain a "Steady State" for hours. This breaks the pipeline automation and sends out false positive alerts.

**Are you currently working around this issue?**
How are you currently solving this problem?

Manually setting the time-out at the Codepipeline "Deploy" stage.

**Additional context**
Anything else we should know?

Related issues:
https://github.com/aws/containers-roadmap/issues/328
https://github.com/aws/containers-roadmap/issues/291

**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 the AWS ECS service and CodePipeline Deploy stage, with related issues 328 and 291 provided as context. Start by reviewing those issues and the ECS steady-state behavior; done would mean an event is sent when most desired tasks are running so the Deploy stage does not falsely time out.

Written by the indexing model from the issue text.