aws-for-fluent-bit : Upgrading chart version leading to Liveness Probe failed

**Describe the bug**

Until now the fluent bit pods were working fine, but the moment I updated my chart from `0.1.19` to `0.1.29` our Fluent Bit pods enter a CrashLoopBackoff state, due to failures in the newly introduced https://github.com/aws/eks-charts/pull/975."

Pod event show the following message

`Liveness probe failed: HTTP Probe failed with statuscode: 500`

**Steps to reproduce**

Spin up an IPv4 EKS Cluster, install the `aws-for-fluent-bit` Chart in version 0.1.29. The pods will enter CrashLoopBackoff.

**Expected outcome**
Liveness probe should be passed with updated chart configuration

**Environment**

Chart name: aws-for-fluent-bit
Chart version: 0.1.29
Kubernetes version: 1.25
Using EKS (yes/no), if so version? Yes, v1.25.12-eks-2d98532

**Additional Context**:

Note： the pods are runing on ec2 node.

Start by reviewing the aws-for-fluent-bit chart's liveness probe configuration in version 0.1.29 and the changes in linked pull request #975. Reproduce the issue on an IPv4 EKS 1.25 cluster, then verify that the probe passes and Fluent Bit pods no longer enter CrashLoopBackOff.

Written by the indexing model from the issue text.