New Container

Fixes #628

PR Checklist

[x] Your PR title follows the Conventional Commits syntax as we make use of this for detecting Semantic Versioning changes.
[x] Your PR allows maintainers to edit your branch, this will speed up resolving minor issues!
[x] The new container is implemented under modules/*
- Your module follows PEP 420 with implicit namespace packages (if unsure, look at other existing community modules)
- Your package namespacing follows testcontainers.<modulename>.* and you DO NOT have an __init__.py above your module's level.
- Your module has it's own tests under modules/*/tests
- Your module has a README.rst and hooks in the .. auto-class and .. title of your container
- Implement the new feature (typically in __init__.py) and corresponding tests.
[x] Your module is added in pyproject.toml
- it is declared under tool.poetry.packages - see other community modules
- it is declared under tool.poetry.extras with the same name as your module name, we still prefer adding NO EXTRA DEPENDENCIES, meaning mymodule = [] is the preferred addition (see the notes at the bottom)
[x] ~The INDEX.rst at the project root includes your module under the .. toctree directive~
[x] Your branch is up to date (or we'll use GH's "update branch" function through the UI)

The current consensus among maintainers is to try to avoid enforcing the client library for the given tools you are triyng to implement.
This means we want you to avoid adding specific libraries as dependencies to testcontainers.
Therefore, you should implement the configuration and the waiting with as little extra as possible
You may still find it useful to add your preferred client library as a dev dependency