UX/Trust Issue: OAuth consent screens expose raw Supabase URL instead of custom domain

[DinanathDash]

Description:
During the onboarding flow, users authenticating via Google or GitHub are shown the raw Supabase project URL (xpdhqqwgprlqmqaqmnyx.supabase.co) on the authorization consent screens rather than the DevHunt domain.

Why this is a critical issue:

• User Trust: Displaying a randomized string domain looks highly suspicious to standard users and resembles a phishing attempt.
• Conversion Rate: This friction point likely causes a percentage of users to abandon the sign-in process entirely.

Steps to Reproduce:

1. Navigate to DevHunt and click "Sign In".
2. Select either the Google or GitHub OAuth option.
3. Observe the redirect/authorization domain listed by the provider (screenshots attached).

Expected Behavior:
The consent screen should indicate that the user is continuing to a DevHunt-branded custom domain (e.g., auth.devhunt.org or devhunt.org).

Suggested Fix:

1. Configure a Custom Domain within the Supabase project settings.
2. Update the authorized redirect URIs in both the Google Cloud Console and GitHub Developer Settings to use the new custom domain instead of the default .supabase.co URL.