[7.17](backport #37725) migrate libbeat pipeline

[mergify]

This is an automatic backport of pull request #37725 done by Mergify.
Cherry-pick of 625ba40 has failed:

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

You are currently cherry-picking commit 625ba402b8.
  (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
	modified:   .buildkite/libbeat/pipeline.libbeat.yml
	modified:   .buildkite/metricbeat/pipeline.yml
	modified:   .buildkite/scripts/common.sh
	new file:   .buildkite/scripts/generate_libbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_metricbeat_pipeline.sh
	modified:   .buildkite/scripts/install_tools.sh
	modified:   .buildkite/scripts/py_int_tests.sh
	new file:   .buildkite/scripts/stress_tests.sh

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   catalog-info.yaml

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

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[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: 13 min 46 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!)