Add Windows 2025 for unit test steps for main branch

[oakrizan]

Proposed commit message

Based on Support Matrix Windows 2025 should be added for filebeat and metricbeat only. Updated Extended Windows unit test group with additional step per beats mentioned above.
Creating a separate PR for main branch and skipping for other branches, since pipeline definitions on 8.x, 8.18 and 9.0 has no test collector plugin enabled.

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

• Relates: Beats Windows 2025 image #43077

Logs

Buildkite filebeat build: https://buildkite.com/elastic/filebeat/builds/14290#0195681f-36ae-41a2-b537-8fdf66f31fba
Buiildkite metricbeat build: https://buildkite.com/elastic/beats-metricbeat/builds/14794#0195681f-3e35-474d-aa8c-ab51ce70a664

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @oakrizan? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[oakrizan]

/test

[v1v]

Please, backport #42998 instead of creating a new PR from scratch. It's not ideal, but I prefer we keep semantic with the backports, so if a PR already is merged with he content and needs to be backported back to other branches, let's use mergify. That's how we can track what changes have been done and where htye have been backported.

[v1v]

see my previous comment and #42998 (comment)

[oakrizan]

Please, backport #42998 instead of creating a new PR from scratch. It's not ideal, but I prefer we keep semantic with the backports, so if a PR already is merged with he content and needs to be backported back to other branches, let's use mergify. That's how we can track what changes have been done and where htye have been backported.

On main branch code is different, it has test collector plugin, while other branches don't

[v1v]

On main branch code is different, it has test collector plugin, while other branches don't

You can create the backport and then modify it afterwards. As I said, the more diligent we are with the processes, the easier the debugging will be when things fail in the future.