SSO misconfiguration - wrong redirection after successful login with root credentials

### Environment

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

### Version

Latest

### Steps to Reproduce

1. Create a personal account
2. Create an organization
3. Configure SSO for organization, eg.: Google SSO
4. Remove/lost SSO configuration (eg.: remove SSO configuration from your GCP account / AWS Cognito)
5. Login with your root credentials to your account.
6. XYZ (organization) requires signing in with Google.

### Expected Result

The user should be able to access the root account and be able to remove the impacted organization from its own account.

### Actual Result

After successful login with credentials (user/password) [Sentry.io]() is redirecting to `auth/login/XYZ/?next=%2Forganizations%2FXYZ%2Fissues%2F` .

It is a misconfiguration and egg-chicken issue.
After removing the SSO configuration in AWS / GCP, you cannot log in to your account because of redirection.
The same issue can happen in the case of changing employers. After leaving typically you can't access your corporate email, which results in blocked access to the root account.

**NOTE:** It is my own organization created and destroyed during Terraform destroy process.
I can't access the account, I can't use the previous configuration/state.