Release 4.x.x

[malcolm-dane]

New Pull Request Checklist

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

Issue Description

Prior to the migration of mongoDB to Mongo Atlas, parse server example could be deployed by a button click. Since the migration this feature disappeared, and debugging nodejs can be a pain and time consuming. When I needed a rapid deployment backend for a project recently I finally had a chance to fix the parse-server-example for Heroku.
This pull request is for Heroku and easy deployment onto their platform for rapid development.

Approach

The approach should be to create a new repo of parse server example that is easily deploy-able onto heroku, or include a shell script to quickly config the stock project for deployment onto Heroku. I have a fork on my profile that I have worked on, that is secure and stripped of conflict causing dependencies. That should be a start, mainly because I know it is stable, and mostly secure.

TODOs before merging

Code cleaning. Documentation. Removing unneeded experiment left overs. Testing to see if any other dependencies can be removed without compromising functions.

• Add tests
• [ X] Add changes to documentation (guides, repository pages, in-code descriptions)
• [X ] Add security check
• Add new Parse Error codes to Parse JS SDK
• A changelog entry is created automatically using the pull request title (do not manually add a changelog entry)

[parse-github-assistant]

Thanks for opening this pull request!

• ❌ Please check all required checkboxes at the top, otherwise your pull request will be closed.

• ⚠️ Remember that a security vulnerability must only be reported confidentially, see our Security Policy. If you are not sure whether the issue is a security vulnerability, the safest way is to treat it as such and submit it confidentially to us for evaluation.

[mtrezza]

Not sure what this PR is based on, but it seems to be not the alpha branch. You may want to rebase your PR. Also the PR title looks weird, why Release 4.x.x?

[malcolm-dane]

Lol I am super confused on how exactly to submit a pull request for that issue we were discussing. I've been really busy and just now got around to checking my git. I wanted to add that I have implemented a working auto mailer soluton that works on heroku and now feel quite confident in this solution.