[7.17](backport #37827) Snapshot packaging stage migration

[mergify]

Proposed commit message

Beats migration to Buildkite issue: https://github.com/elastic/ingest-dev/issues/1693
Links to BK builds:

• Filebeat: https://buildkite.com/elastic/filebeat/builds?branch=oakrizan%3Afilebeat-packaging-stage-migration
• Auditbeat: https://buildkite.com/elastic/auditbeat/builds?branch=oakrizan%3Afilebeat-packaging-stage-migration
• Heartbeat: https://buildkite.com/elastic/heartbeat/builds?branch=oakrizan%3Afilebeat-packaging-stage-migration

Disabled several tests on Windows when running on BK. Related issue: https://github.com/elastic/ingest-dev/issues/3016

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

---

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

[mergify]

Cherry-pick of 01f5a90 has failed:

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

You are currently cherry-picking commit 01f5a90209.
  (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/auditbeat/auditbeat-pipeline.yml
	modified:   .buildkite/auditbeat/scripts/crosscompile.sh
	deleted:    .buildkite/auditbeat/scripts/package-step.sh
	deleted:    .buildkite/auditbeat/scripts/package.sh
	deleted:    .buildkite/auditbeat/scripts/unit-tests-win.ps1
	modified:   .buildkite/auditbeat/scripts/unit-tests.sh
	modified:   .buildkite/env-scripts/env.sh
	deleted:    .buildkite/env-scripts/linux-env.sh
	modified:   .buildkite/env-scripts/util.sh
	modified:   .buildkite/filebeat/filebeat-pipeline.yml
	modified:   .buildkite/filebeat/scripts/integration-gotests.sh
	modified:   .buildkite/filebeat/scripts/integration-pytests.sh
	deleted:    .buildkite/filebeat/scripts/package.sh
	deleted:    .buildkite/filebeat/scripts/unit-tests-win.ps1
	modified:   .buildkite/filebeat/scripts/unit-tests.sh
	modified:   .buildkite/heartbeat/heartbeat-pipeline.yml
	modified:   .buildkite/heartbeat/scripts/integration-gotests.sh
	modified:   .buildkite/heartbeat/scripts/integration-pytests.sh
	deleted:    .buildkite/heartbeat/scripts/package.sh
	deleted:    .buildkite/heartbeat/scripts/unit-tests-win.ps1
	modified:   .buildkite/heartbeat/scripts/unit-tests.sh
	modified:   .buildkite/hooks/post-checkout
	modified:   .buildkite/hooks/pre-command
	new file:   .buildkite/hooks/pre-exit
	new file:   .buildkite/hooks/scripts/util.sh
	new file:   .buildkite/scripts/packaging/package-util.sh
	new file:   .buildkite/scripts/packaging/package.sh
	modified:   auditbeat/module/file_integrity/metricset_test.go

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: .buildkite/filebeat/scripts/package-step.sh
	deleted by them: .buildkite/heartbeat/scripts/package-step.sh
	both modified:   .buildkite/scripts/packaging/package-step.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

• Duration: 44 min 23 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!)