[8.14](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://github.com/elastic/ingest-dev/issues/3072

Logs

• all labels (aws, macos, arm, :Windows): ✅
  entire job: https://buildkite.com/elastic/beats/builds/6193
  packetbeat: https://buildkite.com/elastic/beats-packetbeat/builds/4069
  note: the x-pack/filebeat and x-pack/metricbeat failures are unrelated to this PR are are known failures in 8.14 tracked in https://github.com/elastic/ingest-dev/issues/3208

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

• Duration: 13 min 0 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!)

[dliappis]

@pkoutsovasilis as discussed offline, there is some flakiness with the Python test tests/system/test_file_integrity.py for auditbeat, see e.g. https://buildkite.com/elastic/auditbeat/builds/4174#018f058e-280e-4752-bef4-43edf8886b95/160-343 .
It's been spotted in this PR, but also other PRs. Note that this PR is against 8.14 but we've noticed it also in other branches.