feat: enable head component and native typegen

[wardpeet]

Description

Upgrading Gatsby to latest V4:

• adds support to native head component - removes helmet for React 18 compat (https://www.gatsbyjs.com/docs/reference/release-notes/v4.19/#gatsby-head-api)
• adds support to native query typegen (https://www.gatsbyjs.com/docs/reference/release-notes/v4.15/#graphql-typegen)
• adds extra performance boost by upgrading (https://www.gatsbyjs.com/docs/reference/release-notes/v4.14/#improvements-in-image-and-font-loading-times)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: wardpeet / name: Ward Peeters (5a42fd5)

[wardpeet]

somehow when I ran yarn format I got so many changes and this reduced it a little.

[Urigo]

@orta @hwillson i tried to approve the preview in Netlify but couldn't figure out exactly how, do you know what is the latest flow?

[Urigo]

I get these options but not sure what they are :)

[hwillson]

@Urigo I don't have access to graphql.org's Netlify account, but I'm guessing things aren't configured to automatically allow builds from all PR contributors. The further action options are asking how to proceed since they can't validate the PR creator; e.g. selecting the Approve and add as Git Contributor option will add @wardpeet to the graphql.org Netlify team (details here). This shouldn't be needed though - there are ways to open this up so all PR's auto-build. Do you know who has admin level access for the graphql.org Netlify account? I can help adjust things if we can get access - while we're at it we could also look into getting doc preview builds automatically run as PR checks, with the links auto-added to each PR.

[Urigo]

cc @leebyron can you help us change the setting here?

[Urigo]

ok I got permissions!
Deployed it and everything looks fine for me
Merging