Added HTTP Wait Strategry

[alfkonee]

What does this PR do?

Add an HttpWait Strategy to help wait and Validate HTTP Requests

Why is it important?

Helping to Bring Feature Parity with testcontainers-java

How to test this PR

to Test I'd recommend a simple nginx container setup with the wait strategy setup like so

var nginx =new TestcontainersBuilder<TestcontainersContainer>()
                .WithImage("nginx:latest")
                .WithExposedPort(80)
                .WithWaitStrategy(Wait.ForUnixContainer().UntilHttpSucceed())
                .Build();
await nginx.StartAsync();
await nginx.StopAsync();

[netlify]

✅ Deploy Preview for testcontainers-dotnet ready!

Name	Link
🔨 Latest commit	4758d4e
🔍 Latest deploy log	https://app.netlify.com/sites/testcontainers-dotnet/deploys/63898031a102490009a483f2
😎 Deploy Preview	https://deploy-preview-700--testcontainers-dotnet.netlify.app/api/wait_strategies
📱 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.

[HofmeisterAn]

Thanks for your contribution to OSS and Testcontainers for .NET. We recommend to discuss changes in advance in our main contributing guidelines.

Having an HTTP wait strategy in Testcontainers for .NET would be great. Considering the implementation in Java, I would like to advocate an implementation that follows the Java design. I suggest to split the PR into smaller chunks:

1. Adding a simple builder (MVP) that constructs the HTTP request (using .NET types; probably most can be done with HttpRequestMessage, Uri and UriBuilder).
2. Adding a HTTP wait strategy that sends (invokes) the HTTP request and checks the HTTP status code.
3. Following by a design that checks different HTTP responses.

I would like to avoid any timeout or retry logics in the first implementation. By design we use a CancellationToken to cancel the start up. Timeout and retry logics should be something we support for all wait strategies in the future.

[HofmeisterAn]

I will close this in favor of #717. I've added you as a co-author. Thanks for your contribution.