[tests] More Conformance tests should use Testcontainers

[radical]

.. similar to how others do this.

aspire/tests/Aspire.StackExchange.Redis.Tests/RedisContainerFixture.cs

Lines 11 to 43 in 44a60c1

	public sealed class RedisContainerFixture : IAsyncLifetime
	{
	public RedisContainer? Container { get; private set; }
	public string GetConnectionString() => Container?.GetConnectionString() ??
	throw new InvalidOperationException("The test container was not initialized.");
	public async Task InitializeAsync()
	{
	if (RequiresDockerAttribute.IsSupported)
	{
	Container = await CreateContainerAsync();
	}
	}
	public async Task DisposeAsync()
	{
	if (Container is not null)
	{
	await Container.DisposeAsync();
	}
	}
	public static async Task<RedisContainer> CreateContainerAsync()
	{
	var container = new RedisBuilder()
	.WithImage($"{TestConstants.AspireTestContainerRegistry}/{RedisContainerImageTags.Image}:{RedisContainerImageTags.Tag}")
	.Build();
	await container.StartAsync();
	return container;
	}
	}

aspire/tests/Aspire.StackExchange.Redis.Tests/ConformanceTests.cs

Lines 18 to 19 in 44a60c1

	protected string ConnectionString => _containerFixture.GetConnectionString();

Currently any tests that need to connect get skipped with Unable to connect to server.

• Aspire.Microsoft.EntityFrameworkCore.Cosmos.Tests.
• Qdrant ([Feature]: Add Qdrant test container testcontainers/testcontainers-dotnet#992)
• RabbitMq (already using testcontainers, see [tests] More Conformance tests should use Testcontainers #5254 (comment))

cc @eerhardt @sebastienros @joperezr

[eerhardt]

Qdrant

See testcontainers/testcontainers-dotnet#992

RabbitMq

RabbitMQ is already using testcontainers:

aspire/tests/Aspire.RabbitMQ.Client.Tests/RabbitMQContainerFixture.cs

Lines 34 to 38 in fecfe0a

	public static async Task<RabbitMqContainer> CreateContainerAsync()
	{
	var container = new RabbitMqBuilder()
	.WithImage($"{TestConstants.AspireTestContainerRegistry}/{RabbitMQContainerImageTags.Image}:{RabbitMQContainerImageTags.Tag}")
	.Build();