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

[mergify]

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

• default labels: ✅
  entire job: https://buildkite.com/elastic/beats/builds/6135
  packetbeat: https://buildkite.com/elastic/beats-packetbeat/builds/4055

• all labels (aws, macos, :Windows): ✅
  entire job: https://buildkite.com/elastic/beats/builds/6138
  packetbeat: https://buildkite.com/elastic/beats-packetbeat/builds/4057

  ---

  This is an automatic backport of pull request Migrate packetbeat to static Buildkite pipeline #39087 done by Mergify.

[mergify]

Cherry-pick of 8f8f313 has failed:

On branch mergify/bp/7.17/pr-39087
Your branch is up to date with 'origin/7.17'.

You are currently cherry-picking commit 8f8f3137f2.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .buildkite/hooks/pre-command
	deleted:    .buildkite/scripts/generate_packetbeat_pipeline.sh

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/packetbeat/pipeline.packetbeat.yml
	both modified:   .buildkite/pipeline.yml
	both modified:   .buildkite/scripts/common.sh

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[botelastic]

This pull request doesn't have a Team:<team> label.

[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-22T09:42:49.978+0000

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

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/7.17/pr-39087 upstream/mergify/bp/7.17/pr-39087
git merge upstream/7.17
git push upstream mergify/bp/7.17/pr-39087

[dliappis]

closed in favor of #39110