beats [7.17](backport #38583) replace default images

What is the problem this PR solves?

Jenkins->Buildkite pipelines migration

Replace default images by our own images

Example of the pipelines:

Examples of the affected pipelines:

Related issues

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

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

Apr 05 '24 08:04 mergify[bot]

Cherry-pick of 80dab50f0ce3dafe3125a0587db9465dac5d4fa2 has failed:

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

You are currently cherry-picking commit 80dab50f0c.
  (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/libbeat/pipeline.libbeat.yml
	modified:   .buildkite/metricbeat/pipeline.yml
	modified:   .buildkite/packetbeat/pipeline.packetbeat.yml
	modified:   .buildkite/scripts/cloud_tests.sh
	modified:   .buildkite/scripts/common.sh
	modified:   .buildkite/scripts/generate_libbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_metricbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_packetbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_winlogbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_xpack_auditbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_xpack_dockerlogbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_xpack_filebeat_pipeline.sh
	modified:   .buildkite/scripts/generate_xpack_heartbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_xpack_libbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_xpack_metricbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_xpack_osquerybeat_pipeline.sh
	modified:   .buildkite/scripts/generate_xpack_packetbeat_pipeline.sh
	modified:   .buildkite/scripts/generate_xpack_winlogbeat_pipeline.sh
	deleted:    .buildkite/scripts/go_int_tests.sh
	deleted:    .buildkite/scripts/py_int_tests.sh
	deleted:    .buildkite/scripts/win_unit_tests.ps1
	modified:   .buildkite/winlogbeat/pipeline.winlogbeat.yml
	modified:   .buildkite/x-pack/pipeline.xpack.auditbeat.yml
	modified:   .buildkite/x-pack/pipeline.xpack.dockerlogbeat.yml
	modified:   .buildkite/x-pack/pipeline.xpack.filebeat.yml
	modified:   .buildkite/x-pack/pipeline.xpack.heartbeat.yml
	modified:   .buildkite/x-pack/pipeline.xpack.libbeat.yml
	modified:   .buildkite/x-pack/pipeline.xpack.metricbeat.yml
	modified:   .buildkite/x-pack/pipeline.xpack.osquerybeat.yml
	modified:   .buildkite/x-pack/pipeline.xpack.packetbeat.yml
	modified:   .buildkite/x-pack/pipeline.xpack.winlogbeat.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/auditbeat/auditbeat-pipeline.yml
	both modified:   .buildkite/filebeat/filebeat-pipeline.yml
	both modified:   .buildkite/heartbeat/heartbeat-pipeline.yml
	both modified:   .buildkite/hooks/pre-command
	both added:      .buildkite/scripts/generate_auditbeat_pipeline.sh
	both added:      .buildkite/scripts/generate_filebeat_pipeline.sh
	both modified:   .buildkite/scripts/packaging/package-step.sh
	both modified:   .buildkite/scripts/setenv.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

Apr 05 '24 08:04 mergify[bot]

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

Apr 05 '24 08:04 botelastic[bot]

:green_heart: 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: 16 min 26 sec

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: 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!)

Apr 05 '24 08:04 elasticmachine

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

Apr 05 '24 11:04 mergify[bot]