Make MongoDb Testcontainers (ReplicaSet, Provider, etc) not managing the Docker network at all

As a folliow-up of this discussion: https://github.com/debezium/debezium/pull/4745#pullrequestreview-1612457930

Please make MongoDb Testcontainers (ReplicaSet, Provider, etc) not managing the Docker network at all. A network ( / network's lifecycle) should always be managed outside of containers, not by the testcontainer instances.

Setup and closing of networks was removed in that PR and this task is supposed to take a look if anything is broken in the legacy CI tests that needs to be fixed now. When there is no network set manually Docker will create a default network anyway. So I assume it should be safe to remove the code related to creating and managing Docker network lifecycle management?

That also includes usage of

DockerUtils.enableFakeDnsIfRequired();

and related Mac-specific code. This might be required for Mongo DB on Mac but then it should be hidden inside the container startup on the system environment that needs those commands. Please setup a system-property/build-option that allows disabling this default Fake-DNS activation to allow manual mapping from hosts-file-.