required field on Parse Schema is not handled correctly on special types on the GQL API

[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

When a special field like File is required on the Parse Schema, mutations fails because the GQL type is wrapped by a GraphQL Non Null type.

Steps to reproduce

Add a "required: true" to a special field like a field with a type "File", and attempt a mutation

Actual Outcome

Mutation fails, Parse fail to recognize correctly the special field.

Expected Outcome

Environment

Server

• Parse Server version: 7.0.0
• Operating system: MacOS
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local

Database

• System (MongoDB or Postgres): Mongo
• Database version: 6.0.2
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): FILL_THIS_OUT

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): FILL_THIS_OUT
• SDK version: FILL_THIS_OUT

Logs

[parse-github-assistant]

Thanks for opening this issue!

• ❌ Please fill out all fields with a placeholder FILL_THIS_OUT, otherwise your issue will be closed. If a field does not apply to the issue, fill in n/a.

[parseplatformorg]

🎉 This change has been released in version 7.0.0-alpha.30

[parseplatformorg]

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

[parseplatformorg]

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

[parseplatformorg]

🎉 This change has been released in version 7.1.0