refactor: Security upgrade @parse/push-adapter from 5.1.1 to 5.2.0

[parseplatformorg]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	574/1000 Why? Has a fix available, CVSS 7.2	Use of Weak Hash SNYK-JS-CRYPTOJS-6028119	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: @parse/push-adapter

The new version differs by 4 commits.

• 7d6d874 chore(release): 5.2.0 [skip ci]
• b9a41d1 feat: Add backwards compatibility with APNS payloads when using Firebase Cloud Messaging API (HTTP v1) (How to configure webhooks from stripe to parse server #234)
• 6ceaccc refactor: Upgrade jose from 4.15.4 to 4.15.5 (Add APNS client #235)
• 6032ac3 refactor: bump the npm_and_yarn group group with 2 updates (Split basic type conversions from other logic in transform.js. #233)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Use of Weak Hash

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

Thanks for opening this pull request!

• ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.