Remove Node 12 and Node 17 support

[mtrezza]

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

Node 12 and Node 17 are out of LTS, but its still in the CI and node engine

Feature / Enhancement Description

Remove Node 12 and Node 17 support

Removing Parse Server compatibility would be a breaking change, so this can only be done in Parse Server 6.

Example Use Case

n/a

Alternatives / Workarounds

n/a

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[dblythy]

Is it correct once we remove support for node 12, we can support optional chaining across all files?

[mtrezza]

Yes! Finally

[mtrezza]

Since the Parse JS SDK is a part of Parse Server, it too has to support the same (or a superset of) Node versions. So I guess we'll have to coordinate that breaking change with the Parse JS SDK, make a release and use it as dependency in Parse Server.

[mtrezza]

Closing via #8279