Investigate API Rate Limiting

[mheidinger]

So far PReek has been mostly tested against a GitHub Enterprise Instance in which rate limits seem to be disabled.

It needs to be investigated if rate limits are a potential issue for the app and if so, how they could be implemented. Few Ideas:

• Only fetch first few events for a PR, load more on button press (see #5)
• Make use of rate limiting headers (both REST and GQL) and prevent a refresh if it is hit
• Just show an error message if the response is "rate limit hit"

Documentation:

• GitHub REST API Rate Limiting: https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28
• Notification Endpoint "X-Poll-Interval": https://docs.github.com/en/rest/activity/notifications?apiVersion=2022-11-28
• GitHub GraphQL API Rate Limiting: https://docs.github.com/en/graphql/overview/rate-limits-and-node-limits-for-the-graphql-api

[mheidinger]

Another thought: With #20 do comments still need to be fetched for a review or could they be pulled from the review threads?