ci: build using Github Actions

[cbaker6]

Moves the CI to Github Actions.

• Switch to Parse Alpha branch
• Update codecov
• Update package-lock.json for node 14

[cbaker6]

@dplewis @mtrezza I think this is ready for review.

In terms of the release, I couldn't find this on npm and I see no releases here so I'm assuming it was never released.

Let me know if you see something I missed.

[codecov]

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (b1ab2d3) compared to base (41daf4e).
Patch coverage: 100.00% of modified lines in pull request are covered.

❗ Current head b1ab2d3 differs from pull request most recent head f650f01. Consider uploading reports for the commit f650f01 to get more accurate results

Additional details and impacted files

@@            Coverage Diff            @@
##            master       #35   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          185       187    +2     
  Branches        26        28    +2     
=========================================
+ Hits           185       187    +2     

Impacted Files	Coverage Δ
src/config.js	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[cbaker6]

@dplewis can you review this when you get a chance?

[mtrezza]

Not sure we want to release this as an official product. The last significant commit was made >2 years ago, so we'd first need to make sure this is up-to-date regarding security fixes, etc. We'd also have to add release automation, because it'd be too inefficient to manually maintain this "non-core" repo. Maybe we even need to generally review this, no sure whether this was ever intended to be released as an official product.

There are ongoing discussions that could lead to archiving this repo. Regarding its original purpose, I think it makes more sense to use a 3rd party perf testing tool, it seems to me we're reinventing the wheel here.