[7.17](backport #39871) Migrate github checks to buildkite for packetbeat and x-pack/packetbeat

[mergify]

Proposed commit message

Migrate github checks to buildkite for packetbeat and x-pack/packetbeat

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.

Related issues

• https://github.com/elastic/ingest-dev/issues/3380

Logs

---

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

[mergify]

Cherry-pick of f8679db has failed:

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

You are currently cherry-picking commit f8679db91a.
  (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/packetbeat/pipeline.packetbeat.yml
	modified:   .buildkite/x-pack/pipeline.xpack.packetbeat.yml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: .github/workflows/check-packetbeat.yml

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]

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

[dliappis]

LGTM since this appears to be a clean backport that's passing, but I think we may need to address the equivalent of #39870 (comment) in a subsequent PR?