[7.17](backport #38926) Moved winlogbeat pipeline to central pipeline

[mergify]

Proposed commit message

In scope of https://github.com/elastic/ingest-dev/issues/3072 - moved winlogbeatt pipeline triggering to central pipeline
BK Builds: https://buildkite.com/elastic/beats-winlogbeat/builds?branch=elastic%3Amergify%2Fbp%2F7.17%2Fpr-38926

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 #38926 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 2250273 has failed:

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

You are currently cherry-picking commit 2250273c77.
  (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/pipeline.yml
	modified:   .buildkite/scripts/common.sh

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/winlogbeat/pipeline.winlogbeat.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

[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: 13 min 52 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!)

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[mergify]

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

[dliappis]

Left an ask to move Windows 2016 to the extended group to match what's currently defined in the Jenkinsfile for this branch

[dliappis]

LGTM