feat: support for reusable containers that have been stopped

[edrevo]

This PR allows the reusable-containers feature to reuse stopped containers.

Motivation

I am trying to write integration tests with ClickHouse and Postgres, but I don't want to spin up one container per test. Moving the containers to a static OnceCell works, but unfortunately static variables are not dropped so the containers are not destroyed.

Integrating Ryuk as a solution to works, but the Ryuk container is not able to remove itself. Ryuk will successfully remove all test containers, and then shutdown. In order to avoid generating a Ryuk container per test run, I'd like to use reusable containers. Unfortunately, the current code fail as soon as Ryuk shuts down.

I am actually happy that Ryuk shuts down since that means it won't hog resources. What I want is for the reusable containers to be able to reuse my stopped Ryuk container, since that is the cleanest solution I have found for test container management on OnceCells.

[netlify]

✅ Deploy Preview for testcontainers-rust ready!

Name	Link
🔨 Latest commit	23feb5d
🔍 Latest deploy log	https://app.netlify.com/projects/testcontainers-rust/deploys/694915451ed0120008896455
😎 Deploy Preview	https://deploy-preview-896--testcontainers-rust.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[DDtKey]

I believe it closes #893!

It's actually the desired behavior IMO, thanks for the contribution! 🚀

[DDtKey]

I am trying to write integration tests with ClickHouse and Postgres, but I don't want to spin up one container per test. Moving the containers to a static OnceCell works, but unfortunately static variables are not dropped so the containers are not destroyed

Integration with Ryuk and reusable-containers is the correct direction and we have plans for that for a while. And I really glad to accept PRs towards this direction.

However, as a workaround for your use-case you bc old try to use Weak + Arc combination, so parallel tests will reuse same container - see this example

[edrevo]

Thanks for the quick review! I took a look at the CI failures and it looks due to rate limits on Docker Hub's side.

[DDtKey]

Don't worry about rate limits, we're aware of it and we will resolve it independently

[DDtKey]

Could you address clippy warning?

Generally LGTM!

[DDtKey]

Thank you!