Exclude `:docs:` from publication and BOM

Allow @testcontainers to be inherited from superclass (testcontainers…

…#1843) (testcontainers#2001)

* Updated existing test with now expected behaviour
* @testcontainers is now @inherited

Reduce logs in EnvironmentAndSystemPropertyClientProviderStrate… (tes…

…tcontainers#1913)

Fixes testcontainers#1912

Update .travis.yml to ensure that tag builds are performed

Add "housekeeping" category to the release drafter config (testcontai…

…ners#1652)

Bump httpclient from 4.5.8 to 4.5.9 in /core (testcontainers#1544)

Bumps httpclient from 4.5.8 to 4.5.9.

Signed-off-by: dependabot-preview[bot] <[email protected]>

Adding field name to ExtensionConfigurationException message (testcon…

…tainers#1488)

Fix testcontainers#1391 by using a tagged version of `sshd` (testcont…

…ainers#1407)

Workaround for testcontainers#1406

Add getLogs() to GenericContainer, allowing all logs to be retrieved (t…

…estcontainers#1206)

Fixes testcontainers#1205

Add Toxiproxy module (testcontainers#1330)

Based on https://gist.github.com/rnorth/4c3666d62fa93bf0daa813b282e4ebff, in turn based on [hotels.com’s blog post](https://medium.com/hotels-com-technology/i-dont-know-about-resilience-testing-and-so-can-you-b3c59d80012d) where they show use of Testcontainers with Toxiproxy.

Having seen Toxiproxy and experimented with it, I'm inclined to go with this and suggest that we not move forward with testcontainers#283 (which is a great PR, but we've unfortunately failed to land after quite a long time). While Pumba may be nice and transparent, there are a lot of moving parts and complexity under the covers, vs Toxiproxy, which is a bit less magical but easier to understand.