Add option to convert `Parse.Pointer` in Cloud Function payload

[mtrezza]

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

#8490 was actually a breaking change because it changes the payload in Cloud Functions in a way that a Parse Pointer JSON is converted to a Parse.Pointer instance in the payload, instead of being just a POJO as it used to be previously.

Solution

Add a new Parse Server option that determines whether a pointer should be a POJO (by default), or converted to a Parse.Pointer instance.

Since #8490 is already in beta, and for simplicity, we'll need a refactor PR for both the alpha and beta branch.

Environment

Server

• Parse Server version: 6.3.0-beta.1

References

• feat: Add Cloud Function execution on Parse Object in data browser parse-dashboard#2409 (comment)

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

This PR blocks the stable release pipeline of Parse Server; it fixes a breaking change that has been introduced by mistake.

[parseplatformorg]

🎉 This change has been released in version 6.3.0-alpha.3

[parseplatformorg]

🎉 This change has been released in version 6.4.0-beta.1

[parseplatformorg]

🎉 This change has been released in version 6.4.0-alpha.1

[parseplatformorg]

🎉 This change has been released in version 6.4.0