(aws-batch): EksVolume L2 construct support of PersistentVolumeClaim

### Describe the feature

Hi,

AWS Batch customers would like to use Persistent Volume Claims with their L2 EksVolume CDK constructs.

Related re:Post: https://repost.aws/questions/QUwvOFZ1FDTwiFHxGgXCvYdg/aws-batch-eks-computer-env-with-efs

This ticket is for tracking the enhancement.

### Use Case

> "Now I want to define a job that needs to mount/use an EFS. I have the EFS CSI controller in the cluster, but I don't see any option to use an existing PV and PVC; it only allows using the HostPath."

> "I'm using CDK, this is the options for the EksVolume https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_batch/EksVolume.html"

### Proposed Solution

Add PersistentVolumeClaim to https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_batch/EksVolume.html

Guidance was provided for the customer to use the L1 construct in the meantime: https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_batch/CfnJobDefinition.html#eksvolumeproperty

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### AWS CDK Library version (aws-cdk-lib)

N/A

### AWS CDK CLI version

N/A

### Environment details (OS name and version, etc.)

N/A

Start at the TypeScript AWS CDK EksVolume L2 construct entry point and compare its supported fields with the documented CfnJobDefinition EksVolumeProperty L1 entry point. Check how PersistentVolumeClaim is represented for AWS Batch EKS volumes and verify the construct and its documentation expose it. Done means L2 users can configure an existing PVC.

Written by the indexing model from the issue text.