[CI] CrossClusterEsqlRCS2EnrichUnavailableRemotesIT testEsqlEnrichWithSkipUnavailable failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic-platform-support #5818 / windows-2022_checkpart4_platform-support-windows
• elasticsearch-periodic-platform-support #5808 / windows-2019_checkpart4_platform-support-windows
• elasticsearch-periodic-platform-support #5768 / windows-2019_checkpart4_platform-support-windows
• elasticsearch-periodic-platform-support #5763 / windows-2019_checkpart4_platform-support-windows
• elasticsearch-periodic-platform-support #5763 / windows-2022_checkpart4_platform-support-windows

Reproduction Line:

gradlew ":x-pack:plugin:security:qa:multi-cluster:javaRestTest" --tests "org.elasticsearch.xpack.remotecluster.CrossClusterEsqlRCS2EnrichUnavailableRemotesIT.testEsqlEnrichWithSkipUnavailable" -Dtests.seed=B016FE1422A86EB3 -Dtests.locale=en-SE -Dtests.timezone=America/Creston -Druntime.java=23

Applicable branches:
8.17

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: "connect_transport_exception"
     but: was "node_disconnected_exception"

Issue Reasons:

• [8.17] 5 failures in test testEsqlEnrichWithSkipUnavailable (1.4% fail rate in 358 executions)
• [8.17] 2 failures in step windows-2022_checkpart4_platform-support-windows (16.7% fail rate in 12 executions)
• [8.17] 3 failures in step windows-2019_checkpart4_platform-support-windows (27.3% fail rate in 11 executions)
• [8.17] 4 failures in pipeline elasticsearch-periodic-platform-support (33.3% fail rate in 12 executions)

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

[elasticsearchmachine]

Pinging @elastic/es-search-foundations (Team:Search Foundations)