[7.17](backport #39007) Buildkite Xpack/Winlogbeat pipeline fixes

[mergify]

Proposed commit message

In scope of https://github.com/elastic/ingest-dev/issues/3072 - updated Xpack/Winlogbeat pipeline module test step to use changeset calculation
BK Builds: https://buildkite.com/elastic/beats-xpack-winlogbeat/builds?branch=elastic%3Amergify%2Fbp%2F7.17%2Fpr-39007

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

[mergify]

Cherry-pick of 243f9c3 has failed:

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

You are currently cherry-picking commit 243f9c33d8.
  (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:
	new file:   .buildkite/scripts/changesets.psm1

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

• Start Time: 2024-04-22T14:07:47.943+0000

• Duration: 13 min 39 sec

Test stats 🧪

Test	Results
Failed	0
Passed	3
Skipped	0
Total	3

💚 Flaky test report

Tests succeeded.

🤖 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!)

[mergify]

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

[elasticmachine]

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

[mergify]

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

[dliappis]

LGTM

[dliappis]

LGTM