• chore: handle error in test
• feat: add a first-order package for creating networks

What does this PR do?

This PR creates a new network package that will allow Go users to use the package.New idiom when creating a Docker network with Testcontainers for Go.

This new package exposes functional options representing the former NetworkRequest struct, so that users of the old struct are still able to convert their code to the new format using this deprecation path: instead of creating a Network request, please pass functional options with the needed settings.

As a consequence, the old code to create a network has been deprecated, and will eventually removed in the next major version (v1).

To continue, it's important to mention that the new network will be created with a random name: instead of passing the name as before, we want names to be non-deterministic. And this comes with two benefits:

1. alignment with other Testcontainers libraries
2. users' code won't need to "remember" the network name, simply get the struct returned by the New function, and read the name from there.

Finally, the new network package will have this:

• the New function will return a struct, not an interface as in the previous GenericNetwork: we want to adhere to the Go idiom of "accept interface, return struct" so the consumer of the method can work with the expected, concrete, returned type, not dealing with an abstraction. In other words: producers should produce concrete types to consumers.
• it defines some functional options to configure the creation of the network, also exposing the NetworkCustomizer interface in the case consumers want to define their own options to create the network customising more Docker types. Implementing the Customize function will be enough.
• The WithNetwork functional option used in modules, not released yet, has been moved here and refactored a bit to allow receiving an already created Network struct, and use it in downstream containers.
• A WithNewNetwork functional option to be used in modules has been added. It will create a new network using the functions and options in the network package.

Why is it important?

We want users to create networks with random names. We have stepped-up here to create a new package, which will be a PoC for an eventual v1 release, in which we could have first-order packages for the different entities we manage: networks, images, volumes and containers.

Related issues

• Closes [Enhancement]: create networks using random names #1992

How to test this PR

Please read the docs: https://deploy-preview-1993--testcontainers-go.netlify.app/features/creating_networks/ there we explain how the new APIs are used.

All the modules will receive two new options:

• https://deploy-preview-1993--testcontainers-go.netlify.app/modules/clickhouse/#withnetwork
• https://deploy-preview-1993--testcontainers-go.netlify.app/modules/clickhouse/#withnewnetwork