Certain GraphQL queries do not work with a PAT with "read_api" scope.
<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label:
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
When using a PAT with `read_api` scope, the `currentUser` query returns `null` and the `projects(membership:true)` query returns an empty list of nodes. Using the `api` scope makes those queries work, however, since they are queries and not mutations, I would expect `read_api` to work. It's possibly more queries than those are affected, those are just the ones I happened to be testing.
### Steps to reproduce
1. Make a GraphQL request using this query using a PAT with `read_api` scope:
```
query {
currentUser{
username
}
projects(membership:true) {
nodes {
name
nameWithNamespace
}
}
}
```
2. You will receive this as the result:
```
{
"currentUser": null,
"projects": {
"nodes": []
}
}
```
3. Make the same request with a PAT with `api` scope.
4. The result will contain the requested data.
### Example Project
<!-- If possible, please create an example project here on GitLab.com that exhibits the problematic
behavior, and link to it here in the bug report. If you are using an older version of GitLab, this
will also determine whether the bug is fixed in a more recent version. -->
### What is the current *bug* behavior?
Certain queries do not return data when using a `read_api` scope token.
### What is the expected *correct* behavior?
Queries should work when using a `read_api` scope token.
### Relevant logs and/or screenshots
<!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code
as it's tough to read otherwise. -->
### Output of checks
<!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com -->
#### Results of GitLab environment info
<!-- Input any relevant GitLab environment information if needed. -->
<details>
<summary>Expand for output related to GitLab environment info</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)
(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
</pre>
</details>
#### Results of GitLab application Check
<!-- Input any relevant GitLab application check information if needed. -->
<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:check SANITIZE=true`)
(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
(we will only investigate if the tests are passing)
</pre>
</details>
### Possible fixes
<!-- If you can, link to the line of code that might be responsible for the problem. -->
issue