Fix sign up user in cloud function

[Yurgal]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

Trying to logIn a user using the masterKey and the installationId without using the password

Related issue: #6641

Approach

TODOs before merging

• Add test cases

[mtrezza]

@Yurgal You can click on "Details" to open the test log and see why it failed:

• CI self check has nothing to do with your PR, bump CI env #7352 fixed that --> if you rebase on master or merge master into your branch, it should pass.
• The others fail because of your failing test ;)

[mtrezza]

Can you either move the test into an existing describe group where this fest fits thematically, or if there is no such group, rename this describe group with a short description as you see in the other groups?

If I understand correctly, since the focus here is on auth via cloud code, I would see this test rather in an auth or cloud code spec file. Can you take a look whether there are any tests in auth files that are similar to what you are testing? That would be an indication that your test belongs there.

[Yurgal]

I added it in Auth

[mtrezza]

I think we don't need any fail(), done(), these should be avoided when possible.

[Yurgal]

I don't know how to properly handle the catch issue without fail()

[mtrezza]

• for exceptions use expect().toThrow()
• for promise rejections use expect().toBeRejected()

[Yurgal]

hi @mtrezza

I added a new test. As explain in the java documentation, getSessionToken() using the master key should not return undefined. getSessionToken

[dplewis]

@Yurgal You have to signUp with the installationId otherwise how will login find the user? See tests cases https://github.com/parse-community/Parse-SDK-JS/pull/1031/files

[mtrezza]

⚠️ Important change for merging PRs from Parse Server 5.0 onwards!

We are planning to release the first beta version of Parse Server 5.0 in October 2021.

If a PR contains a breaking change and is not merged before the beta release of Parse Server 5.0, it cannot be merged until the end of 2022. Instead it has to follow the Deprecation Policy and phase-in breaking changes to be merged during the course of 2022.

One of the most voiced community feedbacks was the demand for predictability in breaking changes to make it easy to upgrade Parse Server. We have made a first step towards this by introducing the Deprecation Policy in February 2021 that assists to phase-in breaking changes, giving developers time to adapt. We will follow-up with the introduction of Release Automation and a branch model that will allow breaking changes only with a new major release, scheduled for the beginning of each calendar year.

We understand that some PRs are a long time in the making and we very much appreciate your contribution. We want to make it easy for PRs that contain a breaking change and were created before the introduction of the Deprecation Policy. These PRs can be merged with a breaking change without being phased-in before the beta release of Parse Server 5.0. We are making this exception because we appreciate that this is a time of transition that requires additional effort from contributors to adapt. We encourage everyone to prepare their PRs until the end of September and account for review time and possible adaptions.

If a PR contains a breaking change and should be merged before the beta release, please mention @parse-community/server-maintenance and we will coordinate with you to merge the PR.

Thanks for your contribution and support during this transition to Parse Server release automation!