[Packetbeat] Bump npcap to 1.79

[andrewkroh]

Proposed commit message

Bump the included npcap installer to version 1.79.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

• Relates Bump npcap version to 1.79 golang-crossbuild#378

[andrewkroh]

A backport to 8.12 depends on

• 8.12 being updated to Go 1.20.13
• Bump npcap version to 1.79 (backport #378) golang-crossbuild#379 being merged

[elasticmachine]

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-01-24T21:49:12.495+0000

• Duration: 40 min 55 sec

Test stats 🧪

Test	Results
Failed	0
Passed	17
Skipped	1
Total	18

Steps errors

Expand to view the steps failures

x-pack/packetbeat-packaging-linux - mage package

• Took 8 min 42 sec . View more details here
• Description: mage package

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'hudson.AbortException: script returned exit code 1'

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[efd6]

LGTM, but it would be nice to have the tests pass. Was the builder fix not merge in the parent of this branch?

[andrewkroh]

Broken due to elastic/golang-crossbuild#381 (I put the oem installer exe into the wrong GCS bucket b/c docs were wrong and the builds didn't fail hard when it was missing).

update: The images are fixed now.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 44 min 17 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)