[EKS] [request]: Control Plane Logs to S3

### 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 currently supports control plane logging to CloudWatch Logs (#26), but it would be helpful to support S3 as an alternative log destination. This would be in line with many other AWS services that support logging both to both CloudWatch and S3.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Enabling S3 as a log destination would help with a few issues.

**_Cost_**: CloudWatch Logs is much more expensive than S3 for both ingestion and storage of logs, and it can easily cost in the hundreds of dollars a month to ingest the control plane logs even for a small cluster. In my experience, the **_cost of CloudWatch Log ingestion for many clusters exceeds the cost of EKS itself_**. For customers that have compliance requirements that require the collection of audit logs but do not need all the features of Cloudwatch Logs, archiving logs to S3 would be much more economical.

**_Flexibility_**: Archiving logs to S3 would allow customers that don't use Cloudwatch Logs more flexibility, such as Athena or cost-effective ingestion into another tool like AWS Elasticsearch or Splunk.

**Are you currently working around this issue?**
Ingesting logs through CloudWatch logs, at a much higher cost.

Start by reviewing the existing EKS control-plane logging context, including the referenced CloudWatch Logs issue #26 and the request's cost and flexibility requirements. Done would mean a defined path for supporting S3 as an alternative control-plane log destination, but this roadmap issue does not identify implementation files or tests.

Written by the indexing model from the issue text.