Osquerybeat: Upgrade to osquery 5.12.1

[aleksmaus]

What does this PR do?

Upgrade to osquery 5.12.1.

Why is it important?

Picking up the latest osquery release.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas

Screenshots

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @aleksmaus? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

[pkoutsovasilis]

nit: add a changelog entry to mark when this happened but LGTM

[aleksmaus]

nit: add a changelog entry to mark when this happened but LGTM

yeah, not exactly sure what's up with the current changelog, it was not rotated it seems
still has changes for 8.15
https://github.com/elastic/beats/blob/main/CHANGELOG.next.asciidoc?plain=1#L68

[aleksmaus]

nit: add a changelog entry to mark when this happened but LGTM

yeah, not exactly sure what's up with the current changelog, it was not rotated it seems still has changes for 8.15 https://github.com/elastic/beats/blob/main/CHANGELOG.next.asciidoc?plain=1#L68

Followed up on this, waiting for response.

[aleksmaus]

Another hiccup, osquery schema generation seems to be broken on 5.12.1 branch. I fixed it up, but there is still some data is missing. Will look further today. We use their schema to generate mappings for integration package and readme fields.