Replace graphql tooling with community tools

[BPScott]

The graphql tooling in this codebase predates any community tooling. We didn't use graphql-codegen et al at the time because it didn't exist. Now that community tooling around graphql has gotten much better I would be very interested in seeing if we can leverage community tools now that they exist instead of providing our own tools.

I would prefer it if we leveraged existing tools instead of having to maintain our own. This reduces our maintenance burden and there is more chance that devs shall be familiar with community tooling.

Ideas:

• Replacing graphql-typescript-definitions / fragment matcher generation with https://www.the-guild.dev/graphql/codegen/ / https://www.the-guild.dev/graphql/codegen/plugins/typescript/typescript-operations / https://www.the-guild.dev/graphql/codegen/plugins/other/fragment-matcher
• Replacing graphql-typed with TypedDocumentNode (https://www.the-guild.dev/blog/typed-document-node).
• Replacing @shopify/graphql-testing with @apollo/core/testing
• Deprecating and removing graphql-config-utilities, per https://github.com/Shopify/quilt/issues/2385

I’d like to tackle some of this work after we get Apollo3 rolled out in in #2302 and https://github.com/Shopify/web/pull/68796 (otherwise we end up with too many breaking changes at once). It’s a slow process though.

[macdonaldr93]

+1 graphql-typescript-definitions can't be run in Node 18 because of engine constraints on dependency. It's difficult to work with these packages and the new Apollo packages.