docs(graphql): make object property access safe

[dargmuesli]

See https://eslint.org/docs/latest/rules/no-prototype-builtins.

"it would be unsafe for a webserver to parse JSON input from a client and call hasOwnProperty directly on the resulting object, because a malicious client could send a JSON value like {"hasOwnProperty": 1} and cause the server to crash"

I know that it's unlikely to happen in the Cypress context, but it is always good for developers to see proper prototype access.

[netlify]

👷 Deploy request for cypress-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	0d2a129

[vercel]

@dargmuesli is attempting to deploy a commit to the Cypress Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[dargmuesli]

@jaffrepaul I've rebased this PR to solve merge conflicts. Is there interest to merge this PR?
Edit: @emilyrohrbough maybe you have permissions to get this merged?

[dargmuesli]

@jaffrepaul what can I do to get this merged? 🙏

[vercel]

Deployment failed with the following error:

There is no GitHub account connected to this Vercel account.

[mschile]

Hi @dargmuesli 👋, thanks for the contribution and sorry for taking so long to get it merged!

[dargmuesli]

Thank you!