[ECS] [Longer STOPPED Task Persistence]: Increase cleanup time from 1 hour

### 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**
Currently when an ECS Task is moved to STOPPED the data on ECS side is cleaned up within an hour. Some teams we support want to understand whey tasks stop (usually its OOM or just underlying instance cycle). However by the time they look at the task the data is gone.

The data I'm referring to is:
`aws ecs describe-tasks --tasks xxx --cluster yyy`

**Which service(s) is this request for?**
ECS, Fargate

**Are you currently working around this issue?**
If they really care we ask them to try to wait until it happens again and run the aws command within the hour.