Un-shade docker-java-api

[bsideup]

This PR makes Testcontainers depend on docker-java-api instead of including it into our JAR unshaded. Note that docker-java-core and docker-java-transport-okhttp remain shaded due to their transitive dependencies like Guava or now-in-Kotlin OkHttp.

The transition requires a breaking change in the DockerClientProviderStrategy API and includes a rework.
The rework also includes an improvement that removes one Docker API call (/_ping) and instead reuses the /_info one (reduces the startup by ~200ms).

The dependency graph now looks like this:

While previously it was:

Fixes #1113

[rnorth]

I only had one comment, on a Javadoc change of all things 😂

[dagguh]

Note that docker-java-core and docker-java-transport-okhttp remain shaded due to their transitive dependencies like Guava or now-in-Kotlin OkHttp.

Any plans to unshade it all? I'm still getting nasty classpath clashes:

    java.lang.NoSuchMethodError: com.github.dockerjava.core.DockerClientConfig.getObjectMapper()Lorg/testcontainers/shaded/com/fasterxml/jackson/databind/ObjectMapper;
        at com.github.dockerjava.okhttp.OkHttpDockerCmdExecFactory.init(OkHttpDockerCmdExecFactory.java:124)
        at com.github.dockerjava.core.DockerClientImpl.withDockerCmdExecFactory(DockerClientImpl.java:242)
        at org.testcontainers.dockerclient.DockerClientProviderStrategy.getClientForConfig(DockerClientProviderStrategy.java:177)
        at org.testcontainers.dockerclient.UnixSocketClientProviderStrategy.tryConfiguration(UnixSocketClientProviderStrategy.java:62)
        at org.testcontainers.dockerclient.UnixSocketClientProviderStrategy.test(UnixSocketClientProviderStrategy.java:36)
        at org.testcontainers.dockerclient.DockerClientProviderStrategy.lambda$getFirstValidStrategy$2(DockerClientProviderStrategy.java:118)
        at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:267)
        at java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(StreamSpliterators.java:302)
        at java.util.stream.Streams$ConcatSpliterator.tryAdvance(Streams.java:728)
        at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126)
        at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:499)
        at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:486)
        at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
        at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152)
        at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
        at java.util.stream.ReferencePipeline.findAny(ReferencePipeline.java:469)
        at org.testcontainers.dockerclient.DockerClientProviderStrategy.getFirstValidStrategy(DockerClientProviderStrategy.java:154)
        at org.testcontainers.DockerClientFactory.getOrInitializeStrategy(DockerClientFactory.java:126)
        at org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:147)

I need to be able to use the real DockerClientImpl and TC at the same time. So it seems that TC could either shade it without clashes (org.testcontainers.shaded.com.github.dockerjava.core) or abstain from shading entirely.