feat(ServiceBus): Add support to use existing MSSQL container instances

[lgcmotta]

What does this PR do?

This PR exposes an overload of WithMsSqlContainer, enabling users to attach an existing MsSqlContainer instance to the Azure Service Bus emulator. Previously, ServiceBusContainer automatically spun up its own SQL Server container, leading to unnecessary duplication when users were already testing with Azure Service Bus and SQL Server (see #1323).

Why is it important?

This enhancement addresses the resource usage issues described in #1323. By allowing a single MsSqlContainer to be shared, the overhead of launching a separate SQL Server container to use the Azure Service Bus emulator is eliminated. This can be especially beneficial in CI/CD scenarios or other environments where minimizing resource consumption and reducing test execution time is a priority.

Related issues

• Closes [Enhancement]: Allow Azure Service Bus to use an existent instance of MsSqlContainer #1323

How to test this PR

• A new test has been added that demonstrates attaching a custom MsSqlContainer to ServiceBusContainer.
• Ensure both containers (ServiceBusContainer and MsSqlContainer) are on the same network.
• Use a non-default SQL Server image, for example: mcr.microsoft.com/azure-sql-edge:latest.
• Verify that only the containers you intend to run are launched (Azure SQL Edge for SQL Server, and the Azure Service Bus emulator), and that mcr.microsoft.com/mssql/server:2022-CU14-ubuntu-22.04 (the default in MsSqlBuilder) is not spun up.

Follow-ups

None at this time. Inline summary documentation is included in the new overload.

[netlify]

✅ Deploy Preview for testcontainers-dotnet ready!

Name	Link
🔨 Latest commit	79e36e1
🔍 Latest deploy log	https://app.netlify.com/sites/testcontainers-dotnet/deploys/67a0c39aaad5b80008f7eb9b
😎 Deploy Preview	https://deploy-preview-1335--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.

[HofmeisterAn]

Thanks for the PR. I've slightly rearranged the Build() method and added INetwork as an argument to WithMsSqlContainer(...). I believe it feels more natural for developers to pass the network along with the container instance, as this way they don't have to remember to add the Service Bus Container to the same network. It's more likely to be configured correctly this way, I think. Let me know what you think. I'm happy to merge the PR if you're okay with the changes. Thanks ✌️.

[lgcmotta]

Thanks for the PR. I've slightly rearranged the Build() method and added INetwork as an argument to WithMsSqlContainer(...). I believe it feels more natural for developers to pass the network along with the container instance, as this way they don't have to remember to add the Service Bus Container to the same network. It's more likely to be configured correctly this way, I think. Let me know what you think. I'm happy to merge the PR if you're okay with the changes. Thanks ✌️.

Hey @HofmeisterAn, I agree with you, it makes sense to pass the INetwork with the MsSqlContainer. You can merge these changes!! Thank you for the feedback and contribution to the PR!