fix: await during DockerClientProviderStrategy test method

[KyleAure]

Current behavior

The current test method performs the following socket test:

testcontainers-java/core/src/main/java/org/testcontainers/dockerclient/DockerClientProviderStrategy.java

Lines 209 to 223 in e35705b

	try (Socket socket = socketProvider.call()) {
	Duration timeout = Duration.ofMillis(200);
	Awaitility
	.await()
	.atMost(TestcontainersConfiguration.getInstance().getClientPingTimeout(), TimeUnit.SECONDS)
	.pollInterval(timeout)
	.pollDelay(Duration.ofSeconds(0)) // start checking immediately
	.ignoreExceptionsInstanceOf(SocketTimeoutException.class)
	.untilAsserted(() -> socket.connect(socketAddress, (int) timeout.toMillis()));
	return true;
	} catch (Exception e) {
	log.warn("DOCKER_HOST {} is not listening", dockerHost);
	return false;
	}
	}

Using the config client.ping.timeout

client.ping.timeout = 5 Specifies for how long Testcontainers will try to connect to the Docker client to obtain valid info about the client before giving up and trying next strategy, if applicable (in seconds).

Consider the following scenario where I set client.ping.timeout=60 because my docker host and local machine are in different locales and I expect a network lag.

Duration timeout = Duration.ofMillis(200);
Awaitility
    .await()
    .atMost(TestcontainersConfiguration.getInstance().getClientPingTimeout(), TimeUnit.SECONDS) // do not wait more than 60 seconds
    .pollInterval(timeout) // check status every 200ms
    .pollDelay(Duration.ofSeconds(0)) // start checking immediately
    .ignoreExceptionsInstanceOf(SocketTimeoutException.class) // Ignore the expected timeout
    .untilAsserted(() -> socket.connect(socketAddress, (int) timeout.toMillis())); // Try to connect and timeout after 200ms

Currently, the client.ping.timeout configuration is essentially ignored because the socket will always timeout before atMost is ever reached.

Proposed Behavior

Instead, we should not provide a timeout to socket.connect.
If we take the same example as previously mentioned:

Awaitility
    .await()
    .atMost(TestcontainersConfiguration.getInstance().getClientPingTimeout(), TimeUnit.SECONDS)  // do not wait more than 60 seconds
    .pollInterval(Duration.ofMillis(200)) // check state every 200ms
    .pollDelay(Duration.ofSeconds(0)) // start checking immediately
    .untilAsserted(() -> socket.connect(socketAddress)); // Try to connect with an unlimited timeout

If the client.ping.timeout is reached, then Awaitility will interrupt the Runnable and still throw a ConditionTimeoutException.

[eddumelendez]

Thanks for your contribution, @KyleAure !