feat: prepare data script + pull data into google spreadsheet

[lionel-nj]

This PR provides changes to fetch and prepare data for visualization.

Data

The rest api provided by Github is heavily leveraged to get data from Github repositories

What do we get from there?

1. comment counts / quarter-year
2. number of opened issues / quarter-year
3. number of merged PRs / quarter-year
4. open issues count
5. open PR count

This data is gathered for each of the following repositories:

• MobilityData/gtfs-validator
• MobilityData/transit
• MobilityData/gbfs
• NABSA/gbfs
• google/transit

How is the data transformed into information?

Item from here are counted then classified by quarter of the year.

Technical

• Calls from Github API are asynchronous
  • Octokit is the library used to proceed: it has been developed by Github, has great documentation and mechanisms to automatically paginate over HTTP responses.
  • It is necessary to authenticate when executing the implemented scripts in order to avoid HTTP error 403
• aggregated data is exported as metrics.json files

GCP

This PR comes along with the implementation of a pipeline using Google Cloud Platform that enables automation of data crunching.

View data

• web export: https://docs.google.com/spreadsheets/d/e/2PACX-1vRsOds1l3nNCntabcxqOdvTrVmK1nWjKAsrEoN5gCxB4rqDwrG3j2dDeWgx5pI6m24UGoiG1631fajI/pubhtml
• google spreadsheet: https://docs.google.com/spreadsheets/d/1crXO-U8dUJXiW3TB_SwSJTdiz5hRXAgOGEXyrlxFVjc/edit#gid=303687084

[lionel-nj]

Per discussion with @carlfredl: it would be nice to have google/transit + MobilityData/transit data aggregated all together.

[lionel-nj]

@carlfredl updated this PR following your suggestions.

@maximearmstrong: the PR in question

@heidiguenin according to this PR description, what other indicators could be relevant?

[lionel-nj]

Please note that nice to have items from https://github.com/MobilityData/Tasks/issues/1170 are not implemented yet.

[maximearmstrong]

Overall great job! Just be careful with the style consistency and when possible create constants for the keys/strings that often appear in the code.

[lionel-nj]

Thanks @maximearmstrong for the review! In addition to local installation of Standard JS, what do you think about adding a CI step to check the code syntax? Found this tool that could help us with that.