[Fargate] [request]: support additional log drivers

### 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**
I am using Fargate and I want to log to our ELK cluster.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
With Fargate I got 3 options:
- fluent-bit
- awslogs
- splunk

While fluent-bit in theory can satisfy my requests, I can't handle load well enough (see https://github.com/fluent/fluent-bit/issues/3014).

I would be great to offer alternative log drivers which are less tied into a product. While for example the syslog protocol is not the latest and greatest in logging, at least I can pick between different vendors.

Or don't tie the fluent protocol to fluent-bit, so one could use alternative implementations like https://vector.dev

**Are you currently working around this issue?**
I run fluent-bit to capture stdout/stderr, but I got another side-car to actually handle my logs.

**Additional context**
Someone else also ask for GELF: https://github.com/aws/containers-roadmap/issues/669

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

No repository files, tests, or entry points are mentioned. Start by reviewing the Fargate logging requirements in the issue and the linked GELF request (#669), then determine which additional drivers and implementation scope maintainers would accept; done requires an agreed supported-driver design and corresponding roadmap or implementation work.

Written by the indexing model from the issue text.