Add FAQ that explains why client integrations in the context of aspire.

[davidfowl]

Feedback source: https://www.reddit.com/r/dotnet/comments/1i7zb9l/aspire_consuming_dependencies_question/

FAQ Question:
"If Aspire is mainly for local development, why are client integrations in my project?"

Client integrations in Aspire are designed to make your life easier, not harder. They're lightweight wrappers around popular libraries (like StackExchange.Redis or Npgsql) that add essential features such as telemetry, health checks, and resilience.

Even if you're only using Aspire for local development, these integrations ensure your application benefits from sane defaults and seamless dependency injection.

But here's the catch: you don't have to use Aspire hosting integrations with them. They're just libraries! You can configure them exactly how you would with the underlying libraries, using environment variables or your preferred configuration methods. Aspire doesn't lock you into its ecosystem—it enhances it where you need it.

We should also consider pointing to the FAQ question from the integrations doc.

[maddymontaquila]

did you ask your gpt to say this in a Maddy voice because it sure sounds like something I would write 🤣🤣🤣