Deprectation warning returnOriginal mongo

[Moumouls]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server.

Issue Description

Getting

collection.findOneAndUpdate option [returnOriginal] is deprecated and will be removed in a later version.

Steps to reproduce

Pull master branch and run trigger findOneAndUpdate on db adapter

Actual Outcome

A lot of deprecation warnings

Expected Outcome

No warning

Environment

5.0.0-alpha.1

We need to replace returnOriginal with returnDocument as suggested here: https://jira.mongodb.org/browse/NODE-1812

[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.

[parse-github-assistant]

The label severity:low can only be used in combination with type:bug.

[mtrezza]

Can you please add the parse server version to the issue to clarify. Master branch is changing constantly and an unclear reference. That's why we have alpha releases now.

Why did you consider a deprecation warning to be a bug?

[Moumouls]

@mtrezza related: #7624 (comment)

[Moumouls]

5.0.0-alpha.1

[parseplatformorg]

🎉 This change has been released in version 5.0.0-alpha.2