Add CI check to ensure no devDependency is required in production

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

The CI currently installs all dependencies including devDependendies, which are required to run tests. Therefore, if a dependency is required for a production deployment, but has accidentally been added to devDependendies instead of dependendies, the CI cannot not detect that and Parse Server may crash in a production deployment.

Feature / Enhancement Description

Add CI check that ensures all dependencies that are required for a production deployment are added in under dependendies and none of the devDependendies is required.

Maybe a tool like https://www.npmjs.com/package/dependency-check can make this easy to implement.

Example Use Case

See issue https://github.com/parse-community/parse-server/issues/7786

Alternatives / Workarounds

• manually ensure during review that prod dependency is not added to dev dependency

Start by reviewing the repository's CI configuration and package dependency declarations, then compare the current installation with a production-only installation. The check is done when CI detects any production-required dependency placed in devDependencies, using issue 7786 as the example case if needed.