Docs: OAuth 2.1 Server consent example uses wrong response property (`redirect_to` vs `redirect_url`)

## Bug The [Getting Started with OAuth 2.1 Server](https://supabase.com/docs/guides/auth/oauth-server/getting-started) docs show consent page examples using `data.redirect_to` from `supabase.auth.oauth.approveAuthorization()` / `denyAuthorization()`, but the SDK actually returns `data.redirect_url`. ## Where `apps/docs/content/guides/auth/oauth-server/getting-started.mdx` — multiple code examples, e.g.: \`\`\`tsx const { data, error } = await supabase.auth.oauth.approveAuthorization(authorizationId) // ... window.location.href = data.redirect_to // ❌ undefined \`\`\` ## Source of truth [supabase-js GoTrueClient.ts L5557](https://github.com/supabase/supabase-js/blob/master/packages/core/auth-js/src/GoTrueClient.ts#L5557): \`\`\`ts if (response.data && response.data.redirect_url) { if (isBrowser() && !options?.skipBrowserRedirect) { window.location.assign(response.data.redirect_url) } } \`\`\` ## Impact Following the docs verbatim causes `window.location.href = undefined`, which the browser resolves as a relative URL (`/oauth/undefined` if the consent page is at `/oauth/consent`), creating an infinite redirect loop after consent approval. ## Fix Replace `data.redirect_to` with `data.redirect_url` in all consent examples. The SDK also auto-redirects in browsers by default (unless `skipBrowserRedirect: true`), so the manual `window.location` calls in the examples are technically redundant.