fix: Do not run reusable resource tests in parallel

[HofmeisterAn]

What does this PR do?

This PR addresses a flaky unit test I noticed some time ago. The reusable resource tests (reuse feature) have been flaky, and today I discovered that they interfere with the port forwarding tests. When the port forwarding container is running, Testcontainers automatically injects the necessary extra hosts into the builder configuration using WithPortForwarding() internally. Depending on when the test framework starts the port forwarding container, these extra hosts can cause flakiness. This happens because the reuse hash may change during iterating and creating the container resource(s), resulting in two containers with the same label running instead of one.

I noticed the issue by looking into the actual container configurations and their hashes (see the JSON node ExtraHosts):

// ReuseHash=SwYoG2DcNHf2MEnMvH7tWLmN0Yw=
"RealObject": {
    "Image": {
        "Repository": "alpine",
        "Registry": null,
        "Tag": "3.17",
        "Digest": null,
        "FullName": "alpine:3.17",
        "Name": "alpine"
    },
    "Name": null,
    "Entrypoint": [
        "/bin/sh",
        "-c",
        "trap : TERM INT; sleep infinity \u0026 wait"
    ],
    "Command": [],
    "Environments": {},
    "ExposedPorts": {},
    "PortBindings": {},
    "NetworkAliases": [],
    "ExtraHosts": [],
    "Labels": {
        "71dd3cf7-1df3-4c53-8b9d-8890c93dca85": "7f90fea5-afc3-4e06-8a6a-77638d6640a8",
        "org.testcontainers": "true",
        "org.testcontainers.lang": "dotnet"
    }
}

// ReuseHash=yb7MflZnn0sD0kWz/eiVR/rC9Ao=
"RealObject": {
    "Image": {
        "Repository": "alpine",
        "Registry": null,
        "Tag": "3.17",
        "Digest": null,
        "FullName": "alpine:3.17",
        "Name": "alpine"
    },
    "Name": null,
    "Entrypoint": [
        "/bin/sh",
        "-c",
        "trap : TERM INT; sleep infinity \u0026 wait"
    ],
    "Command": [],
    "Environments": {},
    "ExposedPorts": {},
    "PortBindings": {},
    "NetworkAliases": [],
    "ExtraHosts": [
        "host.testcontainers.internal:172.17.0.14"
    ],
    "Labels": {
        "71dd3cf7-1df3-4c53-8b9d-8890c93dca85": "7f90fea5-afc3-4e06-8a6a-77638d6640a8",
        "org.testcontainers": "true",
        "org.testcontainers.lang": "dotnet"
    }
}

In addition to fixing this issue, the PR aligns two similar tests, now includes the stack trace of an exception in the log message and bumps the test dependencies to their latest version.

Why is it important?

This PR improves the stability and resilience of the CI pipeline and tests.

Related issues

-

[netlify]

✅ Deploy Preview for testcontainers-dotnet ready!

Name	Link
🔨 Latest commit	932c8e8
🔍 Latest deploy log	https://app.netlify.com/sites/testcontainers-dotnet/deploys/66ed97c190ea380008207ffa
😎 Deploy Preview	https://deploy-preview-1267--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 configuration.