[CI] ResolveTransportVersionConflictFuncTest update flag works with multiple branches failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic-platform-support #10661 / windows-2025_checkpart1_platform-support-windows
• elasticsearch-periodic-platform-support #10661 / windows-2022_checkpart1_platform-support-windows

Reproduction Line:

null

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.gradle.testkit.runner.UnexpectedBuildFailure: Unexpected build execution failure in C:\Users\BUILDK~1\AppData\Local\Temp\junit14267434545190315982 with arguments [:myserver:validateTransportVersionResources, :myserver:resolveTransportVersionConflict, --full-stacktrace, -Dtest.external=true]

Output:
=======================================
Elasticsearch Build Hamster says Hello!
  Gradle Version        : 9.0.0
  OS Info               : Windows Server 2025 10.0 (amd64)
  JDK Version           : 21.0.7+6-LTS (Eclipse Temurin)
  JAVA_HOME             : C:\Users\buildkite\.gradle\jdks\eclipse_adoptium-21-amd64-windows.2
  Random Testing Seed   : 6E42DBE2202534B4
  In FIPS 140 mode      : false
=======================================
> Task :myserver:compileJava
> Task :myplugin:compileJava NO-SOURCE
> Task :myplugin:processResources NO-SOURCE
> Task :myplugin:classes UP-TO-DATE
> Task :myplugin:collectTransportVersionReferences
> Task :myserver:generateTransportVersionM
[truncated]

Issue Reasons:

• [main] 2 failures in test update flag works with multiple branches (40.0% fail rate in 5 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

[elasticsearchmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[rjernst]

I think this was addressed by #135978 since windows platform tests are now passing.