GitHub SSO fails on secondary email

# 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 When a user has more than one email address associated with their GitHub account, only the primary address can be used to successfully invite them to the project, even if it is not the email address associated with their Supabase account ## To Reproduce 1. Get access to a GitHub account with 2 different email adresses (common for organisation that allow you to contribute to work projects with your personal account) 2. Create a Supabase account with such a GitHub account, registering a secondary email (not the one the GitHub account was initially created with) as your email 3. Log out and login to another project, not associated with that account 4. Invite the user to the Supabase project, using their Supabase email (=secondary GitHub email) 5. As that user, try to accept the invite 6. Fail with "Your email address xxx@yyy.com does not match the email address this invitation was sent to." ## Expected behavior You should be able to successfully accept invites to either all emails associated with a GitHub account, or at least the email associated with said GitHub account on Supabase. ## System information - OS: chrome on mobile, chrome and firefox on macos - Version of supabase-js: 2.49.4 - Version of Node.js: ? - current hosted version on Supabase.com ## Additional context Add any other context about the problem here.