[ECS] [request]: Draining tasks not replaced for CapacityProviderStrategy when min/max percentage is set for a particular CP

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

This is the use case in which we are facing the isssue:-
Associate 3 capacity providers, each CP should use an ASG which launches instances in only one AZ -

"CapacityProviderStrategy": [
{
"CapacityProvider": "AZ-A",
"Weight": "1",
"Base": "0"
},
{
"CapacityProvider": "AZ-B",
"Weight": "1",
"Base": "0"
},
{
"CapacityProvider": "AZ-C",
"Weight": "1",
"Base": "0"
}
],

* All three CP's are using 100% Target capacity
* Desired Count 2
* Minimum Healthy Percent: 100%
* Maximum Percent: 150%

Now drain one of the EC2 Instance the service gets stuck and the replacement tasks are not launched.

Ideally CP should launch more Instance and then Service scheduler should launch new Tasks on those new Instance.
However Service scheduler launches new Tasks with EC2 launch type with the same deployment configuration, but is getting stuck in this case.

**Which service(s) is this request for?**
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.

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

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

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

Start by reproducing the ECS scenario described in the issue: three capacity providers, a desired count of 2, 100% minimum healthy and 150% maximum percentages, then drain one EC2 instance. Investigate how ECS capacity-provider strategy and service scheduling interact during draining. Done means replacement capacity and tasks launch so the service does not remain stuck.

Written by the indexing model from the issue text.