fix: Remove optional Kubelet monitoring from Container Insights on AWS for FluentBit addon

[rodrigobersa]

What does this PR do?

Motivation

When Container Insights are enabled wiht AWS for FluentBit addon, the aws-for-fluentbit- PODs starting experiencing a CPU spike due logs flooding with the following error:

[error] [filter:kubernetes:kubernetes.0] kubelet upstream connection error

This happens because the access to Kubelet from PODs is not allowed by design on Amazon EKS, being required to add Kubernetes RBAC resources, and update aws-for-fluentbit daemonSet with the paramenter hostNetwork: true. This is an optional feature recommended just for large clusters, as shown in this documentation.

I'll create a documentation here, to guide the deployment of the AWS for FluentBit addon with ClusterInsights Kubelet monitoring enabled.

• Resolves aws-for-fluentbit '/aws/containerinsights/Cluster_Name/performance' log group, but does not create application/dataplane/host log groups. #231

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I ran pre-commit run -a with this PR

For Moderators

• E2E Test successfully complete before merge?

Additional Notes

Customer using the example, validated the solution.