Update octokit client

[roryabraham]

I have been having issues with rate limiting on my PAT, and thought that the source of the issue might be KSv2. The Octokit SDK is supposed to have throttling best-practices built-in, but in the version of octokit we were using, it was commented-out: octokit/octokit.js@v1.7.1...v3.1.1#diff-0b622e16b7fc8551bbe85cced944e28ed91560455e117bfd5a2ffb91fa2731b6L13

So this PR is just updating the octokit client to latest. I tested by:

• running npm i && npm run build
• then in chrome://extensions make sure developer mode is enabled in the top-left corner
• then press Load Unpacked, and choose the dist folder from k2-extension
• Then open K2 and refresh the page. It should all continue to work

• Open an issue and make sure the K2 sidebar appears as normal:

[roryabraham]

Breaking changes 1.0 -> 2.0:

Not affecting us since K2 runs in a browser and not node

Breaking changes 2.0 -> 3.0:

• Node change doesn't affect this repo
• Previews don't either – that's just for the Node REPL
• We don't use agent in octokit.request anywhere in this repo
• This one I'm slightly less confident in, but looking through src/js/lib/api.js, I couldn't find anything that looked like custom request options

[tgolen]

LGTM! Thanks for submitting this. I agree with you that I don't think we are affected by the breaking changes.

@AndrewGable I thought you would get a kick out of Rory finding that this setting was commented out in their source code for the version we were using.

[AndrewGable]

🤣🤣🤣 Great find

[roryabraham]

Realized I forgot to bump the package version and such, uploaded those changes now