bug: rate limit error response from github is not handled

[sentry]

Sentry Issue: STATUS-KEYMAN-COM-1HV

Error: Error parsing {"errors":[{"type":"RATE_LIMIT","code":"graphql_rate_limit","message":"API rate limit already exceeded for user ID 75399505."}]}
  File "/home/site/wwwroot/server/services/github/github-status.ts", line 339
    throw new Error(`Error parsing ${values[ix]}`);
  File "/home/site/wwwroot/server/services/github/github-status.ts", line 335
    let data = keys.reduce((pv, cv, ix) => {
  File "/home/site/wwwroot/server/data/status-data.ts", line 77, in logAsync
    v = await method();
  File "/home/site/wwwroot/server/data/status-data.ts", line 214, in StatusData.refreshGitHubStatusData
    data = await logAsync('refreshGitHubStatusData', () => githubStatusService.get(sprintName));
  File "/home/site/wwwroot/server/code.ts", line 250, in respondGitHubDataChange
    const hasChanged = await statusData.refreshGitHubStatusData('current');
...
(2 additional frame(s) were not displayed)

[mcdurdin]

https://docs.github.com/en/graphql/overview/rate-limits-and-query-limits-for-the-graphql-api#checking-the-status-of-your-primary-rate-limit

We should log the rate limit received from the headers to make this easier to monitor