[7.17](backport #37283) Filebeat pipeline migration to Buildkite

[mergify]

This is an automatic backport of pull request #37283 done by Mergify.
Cherry-pick of 730dc87 has failed:

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

You are currently cherry-picking commit 730dc87d0e.
  (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:
	new file:   .buildkite/env-scripts/env.sh
	new file:   .buildkite/env-scripts/linux-env.sh
	new file:   .buildkite/env-scripts/macos-env.sh
	new file:   .buildkite/env-scripts/util.sh
	new file:   .buildkite/env-scripts/win-env.sh
	modified:   .buildkite/filebeat/filebeat-pipeline.yml
	new file:   .buildkite/filebeat/scripts/integration-gotests.sh
	new file:   .buildkite/filebeat/scripts/integration-pytests.sh
	new file:   .buildkite/filebeat/scripts/package-step.sh
	new file:   .buildkite/filebeat/scripts/package.sh
	new file:   .buildkite/filebeat/scripts/unit-tests-win.ps1
	new file:   .buildkite/filebeat/scripts/unit-tests.sh
	new file:   .buildkite/hooks/pre-command
	modified:   .buildkite/pull-requests.json
	modified:   dev-tools/packaging/package_test.go
	new file:   filebeat/filebeat_windows_amd64.syso
	modified:   filebeat/tests/system/test_crawler.py

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   catalog-info.yaml
	deleted by us:   filebeat/input/filestream/internal/task/group_test.go

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

• Start Time: 2024-02-06T20:44:50.456+0000

• Duration: 215 min 53 sec

Test stats 🧪

Test	Results
Failed	0
Passed	20613
Skipped	1421
Total	22034

💚 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 has not been merged yet. Could you please review and merge it @oakrizan? 🙏

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