[Batch] [Show job state reason and detail in console, CLI and CloudTrail logs]: describe request here

### 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**
1. In the AWS Batch Console, when a job gets stuck in 'RUNNABLE' state in the Status Reason it shows '-'. If you run this command: 'aws batch describe-jobs --jobs through the CLI doesn't return a StatusReason same as the console;
2. In CloudTrail Logs, when you search 'RunTask' you can see the reason, in my case: "reason": "RESOURCE:MEMORY". However to get further details on this reason, I have to contact aws support to get the full logs which also gives us the additional 'details' as below: "detail": "Insufficient memory available (32000 requested, 31431 available).",

**Which service(s) is this request for?**
Batch

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Why I can't easily locate the reason and the detailed part of the reason for troubleshooting and debugging purposes. I can't get a definitive answer for why my job is stuck in RUNNABLE STATE. Why do I need to always contact AWS Support for this information?

**Are you currently working around this issue?**
Yes, in order to get the detailed reason, I have to contact AWS support for their internal logs.

**Additional context**
N/A

Start by comparing the AWS Batch job state information shown in the console and returned by `aws batch describe-jobs` with the `RunTask` details visible in CloudTrail. Done means the status reason and its detailed explanation are available consistently for troubleshooting without contacting AWS Support.

Written by the indexing model from the issue text.