Add rough error handler for Octokit response parsing failures to `1.x` and `2.x` release

This is intended as the 1.x and 2.x equivalent to shipping:

• #258

Addressing #258 will resolve misleading error scenarios where the error message that shows up in the Actions logs says something like HttpError: invalid json response body and reason: Unexpected end of JSON input. This occurs when Octokit receives a response with an error code (e.g. 400) but the accompanying response text is either not JSON-compatible for parsing, or is just not provided at all (empty).

This was resolved in Octokit with the following PR:

• https://github.com/octokit/request.js/pull/648

However, the subsequent Octokit release is not compatible with Node 16.x, and therefore cannot be pulled in as a dependency until we merge #256 and cut a new 3.x release.

Sadly, a new 3.x release won't help all of our GHES customers.

Therefore, we should consider implementing a rough workaround fix (i.e. a catch watching for this exact error) in this scenario so we log fewer "red herring" error messages. 🐟

Start by reviewing #258 and the linked request.js PR 648, then locate the response-parsing path used by the 1.x and 2.x releases. Confirm how Node 16 compatibility constrains the workaround; done means non-JSON or empty error responses no longer produce misleading parsing errors in Actions logs.