Authentication: OAuth user is moved to default org from their own org on first login

### What happened? I create an OAuth user and an org and put that user in their own org, using Grafana API. I checked that the org is created and the OAuth user is only in that org. When the OAuth user logged in, they ended up in the default org instead of their own org. I wonder if this new behavior is related to [this](https://grafana.com/docs/grafana/latest/whatsnew/whats-new-in-v10-1/#oauth-role-mapping-enforcement). ### What did you expect to happen? The user should end up in their own assigned org after log in. ### Did this work before? Yes. It works fine in 10.0.3 Grafana 10.0.3: 1. I create an OAuth user 2. I create an org 3. I assign that user to that org 4. OAuth user logs in and will be in its own org. This is the expected behavior ### How do we reproduce it? Grafana 10.1.1: 1. I create an OAuth user 2. I create an org 3. I assign that user to that org 4. OAuth user logs in and will be in the default org. This is not the expected behavior ### Is the bug inside a dashboard panel? no ### Environment (with versions)? Grafana: 10.1.1 OS: Linux Browser: Chrome ``` "environment": [ { "name": "GF_AUTH_GENERIC_OAUTH_API_URL", "value": "xxx" }, { "name": "GF_DATABASE_PASSWORD", "value": "xxx" }, { "name": "GF_AUTH_GENERIC_OAUTH_TOKEN_URL", "value": "xxx" }, { "name": "GF_AUTH_GENERIC_OAUTH_CLIENT_SECRET", "value": "xxx" }, { "name": "GF_AUTH_SIGNOUT_REDIRECT_URL", "value": "xxx" }, { "name": "GF_DATABASE_USER", "value": "postgres" }, { "name": "GF_SMTP_USER", "value": "xxx" }, { "name": "GF_AUTH_GENERIC_OAUTH_CLIENT_ID", "value": "xxx" }, { "name": "GF_USERS_AUTO_ASSIGN_ORG_ID", "value": "83" }, { "name": "GF_DATABASE_HOST", "value": "xxx" }, { "name": "GF_AUTH_GENERIC_OAUTH_ENABLED", "value": "true" }, …