Hasura Git Deploy OAuth limit

### Version Information

Server Version: N/A
CLI Version (for CLI related issue): N/A

### Environment

### What is the current behaviour?
Currently deploying use Git Deploy uses an OAuth connection to Github. These OAuth tokens are, however, limited to 10 per user/repo combination. After the 11th has been added, the first will get removed. This proves to be a large issue as we are deploying using this system on a regular (sometimes daily) basis. Meaning that there is no way to connect 10+ hasura cloud projects to a single repository.

### What is the expected behaviour?
The capability of providing more than 10 connections to a single repo. This can be done through multiple methods, one of which is already used in the preview app system, using a personal token instead of OAuth. Another would be, as told to me by Github Support that Hasura will handle that the old "removed" connections (after the 10th) should be updated with the new token at Hasura's end.

### How to reproduce the issue?

1. Create 10 projects
2. Link 10 projects with Github Deploy to the same repository and Github user
3. Add an 11th
4. Find out that the 1st (or sometimes random) one gets removed.

### Screenshots or Screencast

See image below for what happens on the 11th connection (Error fetching Github session)


### Please provide any traces or logs that could help here.

### Any possible solutions/workarounds you're aware of?

Using different Github accounts for the OAuth connection, each user can in theory add 10 connections to the same one repo. This, however, combined with GitHub Enterprise licensing cost per user and security reasons is **not** a viable solution.

### Keywords