ci: create properly named accounts to run automated operations

Created by: jhchabran

Original slack thread

Over the past weeks, we hit GitHub rate limits pretty often. When we reach rate limits, GitHub API requests start returning errors. These errors caused issues with the CI, GitHub Actions, and INC-60 (and some customer issues, but I'm not yet up to date on that specific case).

The most immediate solution was creating or using different GitHub accounts to perform the API calls, but this came with the blurriness around GitHub TOS because it means we are creating accounts for the sole purpose of circumventing the rate limits.

I reached out to GitHub support (it took them three weeks to answer) to clarify this, and their answer is crystal clear:

We can create as many GitHub account as we want to compartmentalize calls to the API; (we are paying for them after all).

The GITHUB_TOKEN used in GitHub actions is limited to 1000req/day per repository, and there is no way to check that number as opposed to any other kind of token.

So there is no need to upgrade our current GitHub plan (which would cost us an additional $50k per year), and we can instead use specific accounts ($48 per year) to solve the problem.