feat!: switch to fallible API (#636)

Closes #606

## Migration guide
- The easiest way to use `unwrap` or `expect` for all `testcontainers`
operations.
  - or you can cast error if your tests are already `Result` based
- The `Image::exec_after_start` method returns a `Result`, so if you
have an implementation of `Image` that uses `exec_after_start`, it's
important to handle possible errors (e.g required port not found)

testcontainers/Cargo.toml

@@ -45,6 +45,7 @@ watchdog = ["signal-hook", "conquer-once"]
 properties-config = ["serde-java-properties"]
 
 [dev-dependencies]
+anyhow = "1.0.86"
 pretty_env_logger = "0.5"
 reqwest = { version = "0.12.3", features = ["blocking"] }
 testimages.workspace = true

testcontainers/src/core.rs

@@ -7,12 +7,12 @@ pub use self::{
     mounts::{AccessMode, Mount, MountType},
 };
 
-pub mod errors;
 mod image;
 
 pub(crate) mod client;
 pub(crate) mod containers;
 pub(crate) mod env;
+pub mod error;
 pub(crate) mod logs;
 pub(crate) mod macros;
 pub(crate) mod mounts;