Google Auth Environment Variable Name Conflict in Local Development

# Improve documentation ## Link https://supabase.com/docs/guides/auth/social-login/auth-google?queryGroups=framework&framework=remix ## Describe the problem The documentation for setting up Google OAuth in local development instructs users to set the environment variable as SUPABASE_AUTH_EXTERNAL_GOOGLE_CLIENT_SECRET, but the Supabase CLI explicitly rejects environment variables that start with SUPABASE_ prefix with the following error: ``` Env name cannot start with SUPABASE_, skipping: SUPABASE_AUTH_EXTERNAL_GOOGLE_SECRET ``` This creates a confusing situation where following the official documentation results in the environment variable being silently ignored, causing Google OAuth authentication to fail with an "invalid_client" error. ## Describe the improvement The documentation should be updated to use environment variable names that don't start with SUPABASE_ prefix. For example: Current (incorrect) documentation: ```bash SUPABASE_AUTH_EXTERNAL_GOOGLE_CLIENT_SECRET="<client-secret>" ``` ```toml [auth.external.google] enabled = true client_id = "<client-id>" secret = "env(SUPABASE_AUTH_EXTERNAL_GOOGLE_CLIENT_SECRET)" ``` Suggested correction: ```bash GOOGLE_CLIENT_SECRET="<client-secret>" ``` ```toml [auth.external.google] enabled = true client_id = "<client-id>" secret = "env(GOOGLE_CLIENT_SECRET)" ``` Alternatively, if the CLI behavior is the bug and environment variables starting with SUPABASE_ should be allowed, then the CLI should be fixed instead of the documentation. ## Additional context supabase cli version 2.47.2