ci: Fix failing Node 14 workflow

[dblythy]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

Currently the CI fails on Node 14. When we updated to lockfile v2, there were some manual changes to make it compatible with Node 14. These changes get reverted whenever npm i is ran in another PR.

Closes: n/a

Approach

Adds script to allow npm ci to work on node 14. Can be removed once node 14 is no longer supported.

TODOs before merging

• Add tests

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

Thanks for opening this pull request!

• ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

[codecov]

Codecov Report

Base: 94.04% // Head: 94.32% // Increases project coverage by +0.28% 🎉

Coverage data is based on head (9410b72) compared to base (b1bb1fc).
Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff             @@
##            alpha    #8379      +/-   ##
==========================================
+ Coverage   94.04%   94.32%   +0.28%     
==========================================
  Files         181      181              
  Lines       14266    14266              
==========================================
+ Hits        13416    13456      +40     
+ Misses        850      810      -40     

Impacted Files	Coverage Δ
src/RestWrite.js	94.76% <0.00%> (ø)
src/LiveQuery/ParseLiveQueryServer.js	95.85% <0.00%> (+0.21%)	⬆️
src/ParseServer.js	92.16% <0.00%> (+0.46%)	⬆️
src/Adapters/Files/GridFSBucketAdapter.js	94.20% <0.00%> (+0.72%)	⬆️
src/LiveQuery/ParseCloudCodePublisher.js	100.00% <0.00%> (+15.78%)	⬆️
src/Adapters/Cache/RedisCacheAdapter.js	91.30% <0.00%> (+73.91%)	⬆️

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.

[mtrezza]

@dblythy is it fine if we close this PR in favor of #8381, or do you have any concerns regarding the approach?

[dblythy]

Sounds good!