Adapt CI jobs to new MongoDB lifecycle schedule

[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

MongoDB introduced a new lifecycle concept since MongoDB 5 with "rapid releases". These "rapid releases" are intermediary releases with a minor version increment of the current major version and a reduced lifetime of only 3 months before they reach their end-of-life.

Before MongoDB 5.x, a MongoDB minor version increment contained breaking changes, which was the equivalent of a major version increment in semver. Since MongoDB 5.x, the versioning system follows semver, which means a minor version increment does not contain breaking changes. Therefore there is no need for the CI to test multiple minor versions, it should just test the latest version of a major release.

Feature / Enhancement Description

Parse Server needs to adapt in the following way:

• Remove separate tests for MongoDB minor versions
• Update compatibility table

Example Use Case

n/a

Alternatives / Workarounds

n/a

3rd Party References

• https://www.mongodb.com/support-policy/lifecycles
• https://www.mongodb.com/docs/manual/reference/versioning/

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!