fix: update bollard to version supporting buildkit_providerless

[mbodmer]

fixes: #843

[netlify]

✅ Deploy Preview for testcontainers-rust ready!

Name	Link
🔨 Latest commit	c7949a1
🔍 Latest deploy log	https://app.netlify.com/projects/testcontainers-rust/deploys/68fd64b7ec620b0008f8c500
😎 Deploy Preview	https://deploy-preview-847--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]

@mbodmer may I ask you to check if the test failures are relevant? Looks like all of them are failing and it doesn't look like flakiness at first glance

[mbodmer]

I am using my branch in productive tests. There is no problem with it. It looks like the buildserver takes too long to start the containers. Probably too much load on it.

[DDtKey]

@mbodmer something definitely changed with this PR because all tests are failing, and retries haven’t helped. The errors are also different from the ones we know might be flaky.

  ---- runners::sync_runner::tests::sync_should_return_error_when_non_bridged_network_selected stdout ----
  
  thread 'runners::sync_runner::tests::sync_should_return_error_when_non_bridged_network_selected' panicked at testcontainers/src/runners/sync_runner.rs:130:14:
  called `Result::unwrap()` on an `Err` value: Client(BuildImage { descriptor: "simple_web_server:latest", err: DockerStreamError { error: "debian:bookworm-slim: failed to resolve source metadata for docker.io/library/debian:bookworm-slim: no active session for 01K88X0FRZ8933A0DZATYJGY4P: context deadline exceeded" } })

Many of users will utilize testcontainers in default CI setup, and it doesn't look good
I'd agree if we would see this in current main, but we see this only against providerless version 🤔

[DDtKey]

@mbodmer it wasn't working for me locally too
It worked only if image already present, but building was failing

The issue is wrong execution branch selected, there was one missing place where buildkit feature was required instead of providerless one
I've prepared a fix in bollard: fussybeaver/bollard#597

[DDtKey]

It works here with the patch: #856

[mbodmer]

Thank you for looking into it, i had a short look, but could not make sense of the behaviour. Would have needed more time. Thank you for looking into it!