[ECS] [request]: delay to start container when stopped by target group health check

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

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

we have a container that require sometime for the files lock to get removed,

the issue is, when failed for any reason and started again, some services report that it is already running and doesnt start, so the target group gets unhealty and issue stop command
the next run, other services report that it is already running and doesnt start
and we get into this look for hours
the solution was to shutdown the container manually and start after a minute or two
how can we achieve this automatically? can we have a delay to start a container after one is failed?
**Are you currently working around this issue?**
How are you currently solving this problem?
stop the container and then start it manually after few minutes
**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.)

No files, tests, or entry points are named. Start by reviewing the ECS target-group health-check and container restart behavior described in the issue, then clarify the desired delay semantics and supported configuration. Done would mean the documented capability enables recovery without manually stopping and restarting the container.

Written by the indexing model from the issue text.