Add CI check for package-lock #7326
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
Current, the repo takes the user generated package-lock as is. If package-lock is created by user in local environment with npm 7, there may be issue with older npm versions.
See:
Suggestion
Add CI check that validates package-lock version.