[Feature] Support Aspire

[iancooper]

Is your feature request related to a problem? Please describe. Aspire helps create infrastructure required in dotnet projects. It works well with local developer environments and can be "jailbroken" out to other environments. Aspire fixes a number of issues for us:

• Set up of middleware when using an external bus
• Queue/Topic creation on transports
• Inbox and Outbox Db provisioning
• Schema definition and or migration for Inbox/Outbox

We solve some of these problems via Docker Compose, but this requires managing Docker Compose files to just run our samples. It also does not help if you want to use with K8s instead, etc. We can provision queues and topics for you, but if you want to test code that runs with external provisioning you have to switch flags between local and production environments.

Describe the solution you'd like Brighter support for Aspire in V10.

• Samples use Aspire to provision transports and storage
• Samples use Aspire to provision queues/topics
• Samples use Aspire to create/migrate Inbox and Outbox

Brighter provides custom resources for Inbox and Outbox and uses off-the-shelf for middleware provisioning

Describe alternatives you've considered Avoid using Aspire and continue to use Docker Compose to avoid a .NET silo. Now that Aspire can "jailbreak" we believe it is easier to use first class .NET features over pushing a different route

[iancooper]

Wait in Aspire (useful for Db migration): https://x.com/davidfowl/status/1787696560559792458

[iancooper]

At this point we want to focus on hosts not clients in Aspire. We do not believe integrating with provisioning of clients (Kafka producer, RMQ channel etc.) benefits us, but provisioning of clients does.