Integration docs promote misconception that Aspire is .Net only.

Describe the issue or suggestion

When trying to promote use of aspire within my organisation, I hit the same two misconceptions over and over again

We can't use Aspire as we have components that aren't .Net based
Various forms of "We can't / don't want to use the client integration packages.
- If we only use aspire integration for local dev, why are any aspire packages being shipped to prod
- Aspire's opinionated way doesn't work with us.

The integration docs help encourage these misconceptions. For example the SQL Integration page doesn't have any mention of how to use SQL in non .Net languages.

I'd like to see each of the integration pages include a section on how to use the integrations "raw" within the client - this would apply. For example with SQL, explain how the following could be used to integration with non .Net apps, or for .Net apps that don't fir the .Net Client Integration package opinions.

var app = builder.AddExecutable("app", "whatever", ".")
    .WithReference(db) // connection string becomes the environment variable "ConnectionStrings_{db.Name}"
    .WithEnvironment(c =>
    {
        c.EnvironmentVariables["sql_connectionString"] = db.Resource.ConnectionStringExpression;

        c.EnvironmentVariables["sql_server"] = sql.Resource.PrimaryEndpoint.Property(EndpointProperty.Host);
        c.EnvironmentVariables["sql_port"] = sql.Resource.PrimaryEndpoint.Property(EndpointProperty.Port);
        c.EnvironmentVariables["sql_username"] = "sa";
        c.EnvironmentVariables["sql_password"] = sql.Resource.PasswordParameter;
        c.EnvironmentVariables["sql_database"] = db.Resource.Name;
    });

Which results in the environment variables:

dotnet / docs-aspire

Integration docs promote misconception that Aspire is .Net only. #1763

Describe the issue or suggestion