Old Octokit versions used int rather than long for Issue.Id;
which causes overflow error when parsing responses from the GitHub Issues API.
See octokit/octokit.net#2890

This has two benefits
1) It supports specifying more than one point of interest
   in the interior of the infolog. In a future commit,
   this will be used when an infolog contains more than
   one game with a desync.
2) It has far superior performance.

The new parser identifies regions of the infolog that correspond
to individual games. Each game is further parsed to find:
  GameID
  FirstDesyncIndex
  GameState file names

If the infolog contains GameState file names,
include them in a table in the Issue description.

If the infolog contains multiple games with desyncs, try
to include all of the desync messages in the truncated
infolog.