[ECS/Circuit Breaker]: ability to define for which errors the CB apply

### 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?
The ability to define the errors that will trigger a Circuit Breaker rollback.

**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?**
Circuit Breaker rollbacks for any kind of unhealthy deployments and I would like to specify for which ones to do it. In the case of lack of resources available in the cluster, I want my deployment to be retried until my cluster scales accordingly instead of rolling back.

**Are you currently working around this issue?**
How are you currently solving this problem?
I have to act upon a lack of resources event and retry the deployment after a while.

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