Prepare release of Parse Server 8

[mtrezza]

New Issue Checklist

• Report security issues confidentially.
• Any contribution is under this license.
• Before posting search existing issues.

Issue Description

Task list for release of Parse Server 8.

Tasks

Common

• Remove support for Node versions that have reached their EOL
• Remove support for Postgres / PostGIS versions that have reached their EOL
• Remove support for MongoDB versions that have reached their EOL
• Update package-lock engines.node
  • Specify the exact node version, not just the major version, and use latest Node version, e.g. instead of >=18 <19 || >=20 <21 use >=18.2.3 <19 || >=20.2.3 <21
• Remove deprecated Parse Server options
• Update Snyk branches to monitor
  • Remove current LTS branch, add new LTS branch.
• Update .releaserc.js to new LTS branch

Specific

• refactor: Upgrade @graphql-yoga/node from 2.6.0 to 3.9.1 #9103 (only close, no merge)
• refactor: Bump graphql-upload from 15.0.2 to 17.0.0 #9342

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

@parse-community/server Please feel free to comment for any other things that should be included in the Parse Server 8 release, specially regarding PRs with breaking changes.

[Moumouls]

Not breaking but i'll be happy if we can merge these ones, it's not breaking change but helps developers to achieve advanced uses cases: https://github.com/parse-community/parse-server/pulls/Moumouls

I'll also take a look @mtrezza about differences with my fork, to check if i've some interesting contribution to send to the community repo

I've also a PR idea about avoiding to load some adapters by default if an explicit adapter is provided (for example Postgres is always loaded even if a developer use mongo), it could help to reduce start up time of the server and also reduce integration tests of a developer stack

[mtrezza]

Sounds good!

This thread is specifically about Parse Server 8 preparations (what we can realistically achieve and merge until Dec 2024). The focus here is on breaking changes, as these are easier to do with a major server release.

Everything else can be merged at any point in time after Parse Server 8 release. So all other suggestions, are best discussed by opening separate issues.

Regarding Postgres, see #8715.