chore: commit packages/graphql/schemas/schema.graphql from PR #29420

[MikeMcC399]

• Closes Uncommitted change to packages/graphql/schemas/schema.graphql after PR #29420 #29656

Additional details

• PR fix: HTTP response with invalid headers doesn't throw error #28865 #29420 leaves change to autogenerated packages/graphql/schemas/schema.graphql uncommitted.

Steps to test

Execute:

git clean -xfd
yarn
git status

and confirm that there are no differences reported for packages/graphql/schemas/schema.graphql

How has the user experience changed?

This issue affects contributors only.

PR Tasks

• [na] Have tests been added/updated?
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[jennifer-shehane]

@MikeMcC399 Please avoid merging develop if you can as it extends the time for us to merge in the PRs

[MikeMcC399]

@jennifer-shehane

I'll leave it to you then. I was just doing this because there were CI failures.

[jennifer-shehane]

@MikeMcC399 Yes I know. We can rerun failed only so it's a bit faster. No worries.

[MikeMcC399]

@jennifer-shehane

Thank you for explaining! It would be good to add guidance to the Contributing document about what to do after PR submission, as it is not clear what external contributors should be doing exactly. Let me put this into a new issue to be clear about what questions need to be answered for optimal PR handling.