[EKS] [Logging]: Splunk HEC Support for aws-logging on Fargate

### 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**
EKS aws-logging support for Splunk HEC on Fargate

**Which service(s) is this request for?**
This could be Fargate, EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Send Fargate Pods Stdout Logs directly to Splunk HTTP Event Collector. This output is supported for native FluentBit, but aws-logging options only support lock-in options.

**Are you currently working around this issue?**
I use Cloudwatch Output -> lambda -> HEC but this is a very expensive solution for high tput workloads,

No source files or tests are named. Start by reviewing the EKS aws-logging configuration for Fargate and the requested Splunk HTTP Event Collector output, then define the integration requirements and confirm that pod stdout logs can be sent directly to Splunk without the CloudWatch-to-Lambda workaround.

Written by the indexing model from the issue text.