fix(testcontainers): remove is_running method from testcontainers

Signed-off-by: Raphael Höser <[email protected]>

Author: Snapstromegon

README.md

@@ -13,4 +13,4 @@ Based on the [compliance criteria](https://docs.eventsourcingdb.io/client-sdks/c
 - ❌ [Using EventQL](https://docs.eventsourcingdb.io/client-sdks/compliance-criteria/#using-eventql)
 - ❌ [Observing Events](https://docs.eventsourcingdb.io/client-sdks/compliance-criteria/#observing-events)
 - ❌ [Metadata and Discovery](https://docs.eventsourcingdb.io/client-sdks/compliance-criteria/#metadata-and-discovery)
-- ❌ [Testcontainers Support](https://docs.eventsourcingdb.io/client-sdks/compliance-criteria/#testcontainers-support)
+- 🚀 [Testcontainers Support](https://docs.eventsourcingdb.io/client-sdks/compliance-criteria/#testcontainers-support)

src/container.rs

@@ -219,15 +219,6 @@ impl Container {
         self.api_token.as_str()
     }
 
-    /// Check if the container is running.
-    ///
-    /// Since we make sure the container is running via the typesystem, this will always return true.
-    /// This method is still included to match the interface of the Go SDK.
-    #[must_use]
-    pub fn is_running(&self) -> bool {
-        true
-    }
-
     /// Stop the container
     ///
     /// This will consume the running container and stop it.