Samples should use Aspire where relevant

[TimHess]

Does a sample use multiple applications and/or backing services? Then it should probably use Aspire.

Anticipating little difficulty (excluding the obvious expected framework changes to merging our service discovery features with new APIs introduced alongside Aspire) in this effort, I think we might be able to get away with a single tracking issue - I'm open to any team member editing this issue to add samples or splitting out into separate issues if my hopes are too naive or the effort gets too messy.

• [ ] Discovery
• [ ] ~Freddy's BBQ~ (to be removed rather than updated)
• [ ] ~Music Store~ (to be removed rather than updated)
• [ ] Management

[bart-vmware]

Some guidance to get started on this effort:

• https://devblogs.microsoft.com/dotnet/adding-dotnet-aspire-to-your-existing-dotnet-apps/
• https://devblogs.microsoft.com/dotnet/getting-started-with-testing-and-dotnet-aspire/