NoStackTraceTimeoutException during connection to Kubernetes API server after upgrade to Spring Boot 4.0.3

### Version

vertx: 4.5.14

### Context

Hello Vertx team,

We have met a strange issue since upgrade the Spring Boot to 4.0.3 that calling fabric8 kubernetes client serverSideApply() method failed with a request timeout during connection to the cluster API service.

`Caused by: io.vertx.core.impl.NoStackTraceTimeoutException: The timeout period of 10000ms has been exceeded while executing GET /apis/cluster.x-k8s.io/v1beta1 for server E6F777209F3DCDD41D556D462490F7D4.gr7.us-east-1.eks.amazonaws.com:443`

Which is similar with [an issue reported before](https://github.com/eclipse-vertx/vert.x/issues/5484).

And even the workaround mentioned there to use a okhttp client instead of vert.x works for us...

However, the difference is we don't have such issue with kubernetes 7.X until upgrade the Spring Boot version to 4.0.3 ( or the latest available version 4.1.0 ).

We have raised [an issue for Spring Boot team](https://github.com/spring-projects/spring-boot/issues/50805), but they preferred the issue from vertx...

Thanks!

### Steps to reproduce

_No response_

### Do you have a reproducer?

_No response_

Start by examining the Vert.x request path used by the fabric8 Kubernetes client's serverSideApply() call, focusing on the GET to /apis/cluster.x-k8s.io/v1beta1 and NoStackTraceTimeoutException. Reproduce the timeout across the reported Vert.x and Spring Boot versions, then compare it with the okhttp workaround and issue 5484. Done means the regression is explained and the Kubernetes API request no longer times out unexpectedly.

Written by the indexing model from the issue text.