[AWS Batch on EKS] [request]: For Batch on EKS, how to use/inject/ref Kubernetes secrets for Batch EKS Jobs?

### 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**
For Batch on EKS, how to use/inject/ref Kubernetes secrets for Batch EKS Jobs?

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
For Batch on EKS, how to use/inject/ref Kubernetes secrets for Batch EKS Jobs?
```
spec:
containers:
- envFrom:
- secretRef:
name:
```
Currently, EKS Batch only supports these parameter https://docs.aws.amazon.com/batch/latest/APIReference/API_EksContainer.html
i.e I see an option to specify secret volume into the container https://docs.aws.amazon.com/batch/latest/APIReference/API_EksSecret.html
but does not see an option to specify Kubernetes secret as an Env into the Batch EKS Jobs.

**Are you currently working around this issue?**
I could not find any work around to specify Kubernetes secret as an Env into the Batch EKS Jobs

Start with the AWS Batch EksContainer and EksSecret API references linked in the issue, and compare their documented options with the requested envFrom secretRef configuration. The issue does not name repository files, tests, or an implementation entry point; done would require a decided path for using Kubernetes secrets as environment variables in Batch EKS jobs.

Written by the indexing model from the issue text.