Break up the TestProject to individual projects per Resource/component

[joperezr]

Today, we have a single project which we use for several different component's tests which stands up several containers and services. As discussed offline, we want to break this project apart into individual ones per Resource, which will also allow us to add resource-specific tests to ensure things are working as expected. One example of resource-specific tests, would be to validate that resources that support volumes are working as expected.

@davidfowl has volunteered in taking a first stab at this and separate one resource project to see how it looks like, and we can then parallelize the effort from there.

Components:

• Aspire.Hosting.Azure.Tests
• Aspire.Hosting.Garnet.Tests
• Aspire.Hosting.Kafka.Tests
• Aspire.Hosting.MongoDB.Tests
• Aspire.Hosting.MySql.Tests
• Aspire.Hosting.Nats.Tests
• Aspire.Hosting.NodeJs.Tests
• Aspire.Hosting.Oracle.Tests
• Aspire.Hosting.Postgres.Tests
• Aspire.Hosting.Python.Tests
• Aspire.Hosting.Qdrant.Tests
• Aspire.Hosting.RabbitMQ.Tests
• Aspire.Hosting.Redis.Tests
• Aspire.Hosting.SqlServer.Tests
• Aspire.Hosting.Valkey.Tests
• Aspire.Hosting.Elasticsearch.Tests
• Aspire.Hosting.Keycloak.Tests
• Aspire.Hosting.Milvus.Tests
• Aspire.Hosting.AWS.Tests
• Aspire.Hosting.Dapr

[radical]

It would be useful to add your name next to the item that you want to take, like Aspire.Hosting.Valkey.Tests (assigned: @radical).