[7.17](backport #39087) Migrate packetbeat to static Buildkite pipeline

[dliappis]

Proposed commit message

This commit refactors the packetbeat pipeline to the pipeline selector
approach as laid out in #38783.

Related issues

• https:/elastic/ingest-dev/issues/3072

Screenshots

Logs

• all labels (aws, macos, arm, :Windows):
  NOTE: The failure of x-pack/packetbeat: Load dynamic pipeline's steps — Failed is a pre-existing failure in a job that happened to be triggered due to the files changed in this PR; it will be fixed by the 7.17 backport of move x-pack/packetbeat to static pipeline #39072

  entire job: https://buildkite.com/elastic/beats/builds/6196
  packetbeat: ✅ https://buildkite.com/elastic/beats-packetbeat/builds/4071

Cherry-picked from 8f8f313

[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: 2024-04-22T12:01:33.062+0000

• Duration: 13 min 20 sec

Test stats 🧪

Test	Results
Failed	0
Passed	3
Skipped	0
Total	3

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

[dliappis]

@pkoutsovasilis same comments as in #39108 (comment) re the Auditbeat Python unit tests