Spike: Investigate possible OAuth proxy errors
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=409084)
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=409084)
</details>
<!--IssueSummary end-->
Same as we did for all the other components (see description of the https://gitlab.com/groups/gitlab-org/-/epics/10461 epic), find out the types of errors and describe how we will know about them.
For example (the values are only as an example):
| Error | current state | experiment solution (if different) | viable solution (if different) |
|---|---|---|---|
| Network error between proxy and k8s api server | ? | log error in proxy | fail some health check endpoint|
| Network error between proxy and workspace | ? | log error in proxy, return `503` | |
| Configuration issue (e.g. wrong OAuth client ID) | ? | log error in proxy | |
issue