[7.17](backport #38964) migrate x-pack/libbeat to static

[mergify]

What is the problem this PR solves?

Jenkins->Buildkite pipelines migration

Migrate x-pack/libbeat from dynamic to static pipeline

Examples of the pipelines:
https://buildkite.com/elastic/beats/builds/5828
https://buildkite.com/elastic/beats-xpack-libbeat/builds/2673

Related issues

https://github.com/elastic/ingest-dev/issues/1693

---

This is an automatic backport of pull request #38964 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of b0690b5 has failed:

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

You are currently cherry-picking commit b0690b5fb9.
  (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_xpack_libbeat_pipeline.sh

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/pipeline.yml
	both modified:   .buildkite/pull-requests.json
	both modified:   .buildkite/scripts/common.sh
	both modified:   .buildkite/x-pack/pipeline.xpack.libbeat.yml

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

• Duration: 12 min 27 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]

Windows tests seems to be failing (e.g. https://buildkite.com/elastic/beats-xpack-libbeat/builds/2839#018ef71a-0841-47e8-bae1-faee2bb95956) but the good news is that I think we don't need them at all?

[mergify]

This pull request has not been merged yet. Could you please review and merge it @sharbuz? 🙏

[dliappis]

Basically LGTM.

One final ask, could we remove the reference to xpack-libbeat in the win_unit_tests.ps1 script in the 7.17 branch, now that we've noticed that we don't need Windows tests for this project and branch?

[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-38964 upstream/mergify/bp/7.17/pr-38964
git merge upstream/7.17
git push upstream mergify/bp/7.17/pr-38964

[dliappis]

LGTM