fix: Handle upgrade to logging-operator v4.2.0

[cbuto]

What problem does this PR solve?:
In the logging-operator 4.2.0, the fluent-bit daemonset spec.selector field was updated which is an immutable field.

On upgrade to 2.6, the fluent-bit daemonset is never upgraded because the logging-operator cannot update the DS with the new selectors. The only way to continue is to delete the DS. Unfortunately, since our logging-operator HR is not behind a Kustomization, we don't have a good way of running a job after the operator finishes upgrading so we can't just simply run a kubectl delete on the DS.

By setting enableRecreateWorkloadOnImmutableFieldChange, we allow the operator to recreate resources if required. If this is set, it's recommended to set logging.spec.fluentbit.spec.positiondb and a PVC for the fluentd buffer, both of which we have set.

Which issue(s) does this PR fix?:

https://d2iq.atlassian.net/browse/D2IQ-98592

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Checklist

• If the PR adds a version bump, ensure there is no breaking change in Licensing model (or NA).
• If a chart is changed or app configuration is significantly changed, the chart version is correctly incremented (so that apps are not automatically upgraded from a previous version of DKP).

[d2iq-mergebot]

This repo has @d2iq-mergebot integration. You can perform the following commands by submitting a comment. Submit a comment with content "@d2iq-mergebot help" to view more detailed help text and examples. Be sure the have a look at the mergebot documentation, too.For help using mergebot, please refer to the README file here: https://github.com/mesosphere/mergebot/blob/main/README.md
Enabled Mergebot commands:
@d2iq-mergebot test all
@d2iq-mergebot test
@d2iq-mergebot override-status
@d2iq-mergebot help
@d2iq-mergebot backport