[CI] Netty4TransportMultiPortIntegrationIT testThatTransportClientCanConnect failing

[idegtiarenko]

Seems to happen only on 7.17 and windows-2016

Build scan:
https://gradle-enterprise.elastic.co/s/76ongcrk2ajce/tests/:modules:transport-netty4:internalClusterTest/org.elasticsearch.transport.netty4.Netty4TransportMultiPortIntegrationIT/testThatTransportClientCanConnect

Reproduction line:

gradlew ':modules:transport-netty4:internalClusterTest' --tests "org.elasticsearch.transport.netty4.Netty4TransportMultiPortIntegrationIT.testThatTransportClientCanConnect" -Dtests.seed=137E95DDC3A21473 -Dtests.locale=ar-TN -Dtests.timezone=Etc/UTC -Druntime.java=21

Applicable branches:
7.17

Reproduces locally?:
Didn't try

Failure history:
Failure dashboard for org.elasticsearch.transport.netty4.Netty4TransportMultiPortIntegrationIT#testThatTransportClientCanConnect

Failure excerpt:

java.lang.Exception: Test abandoned because suite timeout was reached.

  at __randomizedtesting.SeedInfo.seed([137E95DDC3A21473]:0)

[elasticsearchmachine]

Pinging @elastic/es-distributed (Team:Distributed)

[cbuescher]

I have another one here on Windows 2016 that seems to result from an OOM.
https://buildkite.com/elastic/elasticsearch-periodic-platform-support/builds/2768#018f831a-412e-43ef-a692-004c4db0417c

I'm looking at several "7.17 and windows-2016" and just want to link another issue I've just observed here: #108755

[pxsalehi]

Setting to medium risk since this is only on windows2016.