[aws-for-fluent-bit] offer lifecycle options to configure preStop

**Is your feature request related to a problem?**
When using Karpenter and node consolidation occurs, Fluent Bit DaemonSet pods may be evicted before application pods, leading to missed logs during the period when Fluent Bit pods are absent but application pods are still running.

**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
aws-for-fluent-bit

**Describe the solution you'd like**
* Add lifecycle section to `stable/aws-for-fluent-bit/values.yaml` and `stable/aws-for-fluent-bit/templates/daemonset.yaml`.
* Expanding terminationGracePeriod is also required.

**Describe alternatives you've considered**
n/a

Start with stable/aws-for-fluent-bit/values.yaml and stable/aws-for-fluent-bit/templates/daemonset.yaml to trace how DaemonSet pod settings are configured. Confirm the lifecycle and termination settings needed for preStop during node consolidation, then verify the rendered chart exposes them and supports the required termination grace period.

Written by the indexing model from the issue text.