Update `githubIssues.js` task to pull issues from a Google Spreadsheet instead?

[alykat]

The CSV in the repo is great, but, depending on the complexity of what we want to put into the default text, editing it is kind of a pain. An alternate idea could be to point to a Google Sheet, automatically d/l a CSV from there, and then continue on with the task?

This is a pretty minor nice-to-have.

[thomaswilburn]

Might be worth pulling from an ArchieML doc instead--you'd want to set up the relevant tasks to export their internal mechanisms in a way that could be could be imported elsewhere (maybe by adding them onto the function that they're already exporting as properties, or by moving that code into tasks/lib the way the Chalkbeat rig does with S3 now), but once that's done it'd be pretty easy to pull that down and convert it into the same structure that the GH task currently expects.