feat(fluent-bit): Updated image to v3.1.10

[edsiper]

The following PR updates the Fluent Bit image to the latest version available: v3.1.10:

• https://fluentbit.io/announcements/v3.1.10/

In addition, I am reverting the change that was done in the PullPolicy for the main image from 'IfNotPresent' to 'Always'. As you know, we don't do user-telemetry in Fluent Bit, our only indicator of adoption is the number of deployments/downloads from the containers registry. Users can always tweak this value, so I am just changing the default as the one we had before.

[stevehipwell]

@edsiper changing the pull policy like this is a major issue given that the image is hosted on Docker Hub where the rate limit is aggressively low. Also given the vanity OCI registry needs explicitly authenticating with Docker credentials even clusters with Docker auth configured correctly make be impacted. I'm speaking from experience here.

Also I can't see a valid use case for this being required to get a correct usage for FB? If the image hasn't changed and it still exists on the node then the only change was a configuration one and shouldn't add another "download".

[edsiper]

@stevehipwell the main reason to bring that value Always back is pretty much to revert the change that was done in April this year in this commit. For years we set to Always as a mechanism to measure Fluent Bit adoption in containerized environments, since that change we lost the metrics, and I think this is the less invasive than adding user-telemetry in the project.

Just reverting to what was working from a maintainers/ecosystem perspective until we have a better solution, anyways this can be easily changed by the user.

[stevehipwell]

@edsiper that setting was a hangover from when the image version wasn't immutable (e.g. latest), when it was required. If the download numbers changed after this change it just means that the numbers were never correct; index pulls do not equal downloads.