[Packetbeat] Fix BPF filter setting not being applied to sniffers

[taylor-swanson]

What does this PR do?

• Ensures that the BPF filter setting is applied to sniffers

Why is it important?

BPF filters were not being applied to pcap and af_packet sniffers and were processing packets that were supposed to be filtered out.

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.

How to test this PR locally

• Configure packetbeat to sniff an interface with either the pcap or af_packet (Linux only) type and configure a BPF filter. Turning on debug logging will either show packets being handled or the sniffer timing out. If you configured the BPF filter to handle traffic known to not exist, then you should see the sniffer time out. If the BPF filter had not applied properly, then it would be picking other traffic (this is especially the case if you connect to the test host using SSH).

Related issues

• Closes [Packetbeat] bpf_filter setting does not work in packetbeat 8.x. #35363

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @taylor-swanson? 🙏.
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/security-external-integrations (Team:Security-External Integrations)

[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

• Start Time: 2023-05-16T15:43:58.816+0000

• Duration: 51 min 48 sec

Test stats 🧪

Test	Results
Failed	0
Passed	1748
Skipped	19
Total	1767

💚 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!)