feat: Update graphql yoga to v3

[ardatan]

New Pull Request Checklist

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

Issue Description

Hi @parse-community team!

We recently released v3 of GraphQL Yoga with bunch of improvements and new features.
You can see the changelog and also the migration guide for all the changes done between v2 and v3.

Migration guide; https://www.the-guild.dev/graphql/yoga-server/v3/migration/migration-from-yoga-v2
Changelog; https://github.com/dotansimha/graphql-yoga/blob/v3/packages/graphql-yoga/CHANGELOG.md

Related issue: #8314
Closes: #8314

Approach

• Replace @graphql-yoga/node with graphql-yoga
• Remove cors middleware because graphql-yoga handles CORS already
• Refactor server instantiation code because Yoga accepts schema factory functions as schema in v3

TODOs before merging

• Add tests

[parse-github-assistant]

Thanks for opening this pull request!

• 🎉 We are excited about your hands-on contribution!

[mtrezza]

Thanks for opening this PR

Even if it is Beta, it is production ready and we already started using it in production for months. It is still Beta because we think we might introduce some breaking changes in the API in the meanwhile :)

We'll wait until it is published as stable release before merge, but great that you opened the PR already so we can prepare.

[mtrezza]

Hi there, we are preparing the Parse Server 6 release this month. If this PR contains any breaking changes, this would be a good time to merge it. The next opportunity for merging breaking changes (without deprecation) will be end of 2023.

cc @Moumouls for this GraphQL PR

[Urigo]

@mtrezza we are very close to major, please wait for us so we can push this forward!
How long do we have to finish it until Parse Server 6?

[Urigo]

also, can you please approve the workflow so we can have a view into the current state?
thanks

[mtrezza]

Could you resolve the conflicting files, so I can run the workflow?
Planned deadline for PRs to merge for Parse Server 6 is Dec 1st. Do you have an ETA for the major release?

[parse-github-assistant]

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

[ardatan]

@mtrezza Rebased the conflicts

Planned deadline for PRs to merge for Parse Server 6 is Dec 1st. Do you have an ETA for the major release?

I think we will probably release it before December 1st.

[mtrezza]

Let's coordinate then, you can keep us updated here or reach out to me directly via our Slack.
Could you open an issue that refers to this PR, so I can track it in our TODO list for Parse Server 6?

[Moumouls]

@ardatan @mtrezza i'll take a look also to the changeling of yoga V3 before merging this 🚀

Thanks @ardatan for the pr :)

[mtrezza]

I've opened #8314 to track this for our Parse Server 6 release.

[ardatan]

Is there anything we can help here to get this merged?

[mtrezza]

Resolving the conflict would be good

[ardatan]

Done!

[mtrezza]

The package-lock.json file was created with an old version of npm,

The lockfile is v1; we have #8274 that will bump it to v2 on the alpha branch, but it's still in the works. You could either wait until the PR is merged, or use Node <=14 when you run npm i.

[mtrezza]

We are nearing the feature freeze of Parse Server 6. What's missing in this PR to merge it?

[mtrezza]

@ardatan We have merged the upgrade to lock-file version 2. Could you rebase this PR on the latest commit? This should solve the install issue.

[Moumouls]

@ardatan @mtrezza with have some deep fails also related to the custom schema system, i will not be able to take a deep look until mid January, btw @mtrezza this PR should be okay to be in Parse V6 later since it will not introduce any breaking changes to interfaces exposed to Parse developers. It's just an internal refactoring as i can see

[mtrezza]

it will not introduce any breaking changes

Thanks for clarifying, I was going with @ardatan's comment, but he probably meant the internal API:

It is still Beta because we think we might introduce some breaking changes in the API in the meanwhile :)

So I'll remove the breaking label and I'll also remove this from the "planned changes" list of PS6.

[mtrezza]

What is the status of this PR? Can we get this ready for merge?

[ardatan]

If you help us with failing tests, we'd love to proceed.

[mtrezza]

@parse-community/server heads up to GraphQL developers; this PR needs a helping hand to upgrade the GraphQL API