Fix: HTTP wait strategy does not take query params into account

[benja-M-1]

What does this PR do?

When specifying a wait strategy using HTTP with query params, they are not sent to the container.
For example, to ensure the elasticmq container is ready, as advised in this issue, one must
poll the /?Action=ListQueues endpoint.
Currently this returns a 400 Bad request because the query parameters are not sent correctly to the endpoint.

The way the fix work is to parse the given path to create a url.URL instance and update the fields with the other values. This way the query parameters and the path are correclty handled.

Why is it important?

Related issues

Here is a reproduction with the elasticmq container:

req := testcontainers.ContainerRequest{
	Image:        "softwaremill/elasticmq-native:1.5.7",
	ExposedPorts: []string{"9324/tcp"},
	WaitingFor:   wait.ForHTTP("/?Action=ListQueues").WithPort("9324").WithStartupTimeout(3 * time.Second),
}

genericContainerReq := testcontainers.GenericContainerRequest{
	ContainerRequest: req,
	Started:          true,
}

c, err := testcontainers.GenericContainer(ctx, genericContainerReq)
if err != nil {
	return fmt.Errorf("failed to start repos-new elasticmq container: %w", err)
}

[netlify]

✅ Deploy Preview for testcontainers-go ready!

Name	Link
🔨 Latest commit	d24da57
🔍 Latest deploy log	https://app.netlify.com/sites/testcontainers-go/deploys/660e894e37784000080b8855
😎 Deploy Preview	https://deploy-preview-2466--testcontainers-go.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 configuration.

[mdelapenya]

LGTM, thanks!