feat(#493): Add container lifecycle events

[HofmeisterAn]

What does this PR do?

The PR allows to override the DockerContainer lifecycle members (StartAsync, StopAsync, UnsafeCreateAsync, UnsafeDeleteAsync, UnsafeStartAsync, UnsafeStopAsync). This allows modules to extend or change the default lifecycle behavior to the module requirements. The Unsafe* members are protected and not thread-safe. Their public entrypoints are thread-safe though. This is necessary otherwise we end up with nested locks which are bad. The implementation takes care that the Unsafe* members are called in a thread-safe environment.

The PR adds the events Creating, Starting, Stopping, Created, Started, Stopped to the IContainer interfaces. Developers can subscribe to those events and get notified soon as the container reached the respected state.

Refactors the Guard implementation to support various different use cases. PR makes Guard public.

Why is it important?

To allow developers access to the different resource lifecycles.

Related issues

• Relates Publish dedicated modules (pre-configured containers) #493

Breaking Changes

The interface IWaitUntil.Until(IContainer, ILogger) has changed to IWaitUntil.UntilAsync(IContainer). The logger is now available through the Docker resource instance. Providing backwards compatibility is cumbersome. Adding an interface member requires a change anyway. It is easier to simply change the interface name and remove the ILogger arg.

[netlify]

✅ Deploy Preview for testcontainers-dotnet ready!

Name	Link
🔨 Latest commit	2699650
🔍 Latest deploy log	https://app.netlify.com/sites/testcontainers-dotnet/deploys/63d12441fea7fe0008565792
😎 Deploy Preview	https://deploy-preview-743--testcontainers-dotnet.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 settings.