Issue with logging in with different accounts

### Environment

SaaS ([https://sentry.io/](https://sentry.io/))

### Steps to Reproduce

1. Have a GitHub account that has two email addresses associated with it: EmailA and EmailB

Create a Sentry account (SentryA) where you login using Google with EmailA. This is a work account and also has 2fa turned on, but I do not think that is relevant.

1. Create a Sentry account (SentryB) where you login using GitHub with EmailB. This is a personal account and 2fa is not turned on.
2. Use the GitHub integration with both Sentry accounts (SentryA and SentryB).
3. Try to login with Google to SentryA.
4. Try to login with GitHub to SentryB.

### Expected Result

1. When you try to login to SentryA with Google, you can. This will have your orgs and projects related to EmailA, but will be able to work with the GitHub integration.
2. When you try to login to SentryB with GitHub, you can. This will have your orgs and projects related to EmailB, but will be able to work with the GitHub integration.

### Actual Result

1. When you try to login to SentryA with Google, you are put in an authentication loop that leads you back to the login page with no error messages. If you try again too many times you are re-directed to a blank page that says `429 Too Many Requests`. Clicking a link from a Sentry notification (e.g. in email or Slack) takes you back to the login page, which then starts the auth cycle again.
2. When you try to login to SentryB with GitHub, you are re-directed back to the login page with no error messages. If you have gone through the authentication process, even though you are re-directed back to the login page, you can go *directly* to another part of the app (e.g. [https://sentryb.sentry.io/issues/](https://sentryb.sentry.io/issues/)) and be authenticated and engage with Sentry as expected.

### Product Area

Sign In

### Link

*No response*

### DSN

*No response*

### Version

*No response*