Update fluent-bit to 3.1.9 and allow lua plugin

[paulmey]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• [x] The toolchain has been rebuilt successfully (or no changes were made to it)
• [x] The toolchain/worker package manifests are up-to-date
• [x] Any updated packages successfully build (or no packages were changed)
• [x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• [x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• [x] All package sources are available
• [x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• [x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• [x] All source files have up-to-date hashes in the *.signatures.json files
• [x] sudo make go-tidy-all and sudo make go-test-coverage pass
• [x] Documentation has been updated to match any changes to the build system
• [x] Ready to merge

---

PR Description

Enabled the lua filter plugin which was previously disabled because it pulled in a copy of the luajit library, which it wanted to install. https://github.com/fluent/fluent-bit/pull/7286 (in 3.1.5) makes it possible to use the system luajit library instead of the vendored version. With this change, the lua filter plugin can be built with the system luajit library.

Also, according to https://fluentbit.io/announcements/older-versions/, the 3.0 line went EOL on Sep 11 2024.

• Updated fluent-bit to upstream 3.1.9. Enabled use of lua filter plugin with system luajit library.
• Fixes #10675

Test Methodology

• Fix verification
  • Tested local RPM build with %with_check=1
  • Impacted user verification - xxxx
• Package Tests
  • Package build & ptest - xxxx
  • Upgrade/downgrade test - xxxx
• Scenario Test results (or explain why the scenario does not need to be tested)
  • AKS: xxxx
  • Azure VM: xxxx
  • BVT: xxxx
  • BareMetal: xxxx
  • ISO: xxxx
  • Container: xxxx

Regression Risk

To the best of your knowledge, where might potential problems/regressions arise?

According to Upgrade Notes | Fluent Bit: Official Manual, there have not been any breaking changes for a long time. None of the release notes between 3.0.6 and 3.1.9 mention any breaking changes either.

Does this affect the toolchain?

NO

Relevant links

• https://github.com/fluent/fluent-bit/pull/7286
• https://fluentbit.io/announcements/older-versions/
• https://docs.fluentbit.io/manual/installation/upgrade-notes