feat: reusable containers

[the-wondersmith]

PR implements reusable containers inline with the existing reusable containers feature(s) of testcontainers for other languages.

Important

This PR follows from (and is branched from) #756. PR 756 must be merged prior to merging this PR

[netlify]

✅ Deploy Preview for testcontainers-rust ready!

Name	Link
🔨 Latest commit	bc3142f
🔍 Latest deploy log	https://app.netlify.com/sites/testcontainers-rust/deploys/67603e8772fff90008589e34
😎 Deploy Preview	https://deploy-preview-757--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 site configuration.

[the-wondersmith]

@DDtKey Dug into the test failures, and it looks like it's just cargo hack not including experimental when it tries to activate the reusable-containers feature.

I updated the CI action to fix it, but (for obvious reasons) GHA won't run actions from forks / PR branches (usually).

Not sure how to proceed here, got any thoughts?

[DDtKey]

Actually, I think we can avoid usage of experimental feature.
It's already under separate feature and we can just claim in documentation that it's "experimental" functionality. It's not enabled by default and users anyway should read something about the feature before enabling it.

But regarding your question, CI works with your changes (if I got you correctly):
https://github.com/testcontainers/testcontainers-rs/actions/runs/12200812163/job/34037798890?pr=757

running `cargo test --no-default-features --features experimental,reusable-containers` on testimages (67/67)
  error: the package 'testimages' does not contain these features: experimental, reusable-containers
  help: package with the missing features: testcontainers

It fails on testimages. For testcontainers all tests have passed as far as I can see.

[the-wondersmith]

Actually, I think we can avoid usage of experimental feature. It's already under separate feature and we can just claim in documentation that it's "experimental" functionality. It's not enabled by default and users anyway should read something about the feature before enabling it.

Fair enough. Removed the experimental feature and reverted the CI changes 🙂

[DDtKey]

Thank you for all efforts! ❤️

I've left a few comments, please take a look

[DDtKey]

I like what you've built here. Thank you a lot and sorry for all the delays 🙏

Only few minor comments and LGTM

Next milestones for this feature are:

• env-variable control
• proper reaper for "current session" (ryuk)