[7.17](backport #38135) Migrate xpack packetbeat

[mergify]

What is the problem this PR solves?

Jenkins->Buildkite pipelines migration

Migrate x-pack packetbeat pipeline

Example of the pipelines:
beats-xpack-packetbeat
Examples of the affected pipelines:
beats-libbeat
beats-metricbeat
beats-packetbeat
beats-winlogbeat
beats-xpack-libbeat
beats-xpack-metricbeat

Related issues

https://github.com/elastic/ingest-dev/issues/1693
#38142 - related to commented-out Windows system tests

---

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

[mergify]

Cherry-pick of e0d5fe5 has failed:

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

You are currently cherry-picking commit e0d5fe5fef.
  (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/scripts/common.sh
	modified:   .buildkite/scripts/generate_xpack_metricbeat_pipeline.sh
	new file:   .buildkite/scripts/generate_xpack_packetbeat_pipeline.sh
	modified:   .buildkite/scripts/win_unit_tests.ps1
	modified:   .buildkite/x-pack/pipeline.xpack.packetbeat.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/scripts/setenv.sh
	both modified:   x-pack/packetbeat/magefile.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

[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: 14 min 11 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!)

[sharbuz]

I've removed changes of the x-pack/packetbeat/magefile.go because in 7.17 I don't see these tests.
@pierrehilbert please correct me if I'm wrong...

[pierrehilbert]

As packetbeat is owned by @elastic/sec-linux-platform, @nfritts will probably know more about that. But if you didn't find those tests, this is probably true.

[mergify]

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

[jlind23]

Merging this according to the slack convo we had with @sharbuz and @dliappis