Kakao OAuth fails for individual developers - account_email scope requires business app

# Bug report - [x] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the [Docs](https://docs.supabase.com), GitHub [Discussions](https://github.com/supabase/supabase/discussions), and [Discord](https://discord.supabase.com). ## Describe the bug Kakao OAuth authentication fails for individual developers because Supabase Auth requests the `account_email` scope by default, which is only available for business-verified applications in Kakao's developer platform. Individual developers cannot use this scope, causing OAuth login to fail with error KOE205. **Update**: A workaround has been discovered (see Additional Context), but this critical information is missing from Supabase documentation, causing many developers to abandon Kakao OAuth implementation. ## To Reproduce Steps to reproduce the behavior 1. Create a Kakao application as an individual developer (not business-verified) 2. Follow the [Supabase Kakao OAuth documentation](https://supabase.com/docs/guides/auth/social-login/auth-kakao) 3. Set consent items in Kakao console: `account_email`, `profile_image`, `profile_nickname` (as documented) 4. Attempt to sign in with Kakao OAuth 5. See error: "잘못된 요청 (KOE205) - 설정하지 않은 카카오 로그인 동의 항목을 포함해 인가 코드를 요청했습니다. 설정하지 않은 동의 항목: account_email" ## Expected behavior Either: - OAuth should work for individual developers without requiring business verification - Documentation should clearly state that business app verification is required - Alternative setup instructions should be provided for individual developers ## Screenshots  ## System information - This issue is platform-independent (OAuth server-side configuration) ## Additional context ### Related Issues - #29917 - Previous report of the same issue (closed due to inactivity) - Solution suggested by @woodwardryan: "Register as Individual" option in Kakao Business settings ### Current …