[EXAMPLES] Update with-apollo-neo4j-graphql

[mjfwebb]

We replace neo4j-graphql-js with @neo4j/graphql and update Apollo server to version 4.

This refactor also changes the code from Javascript to Typescript.

Bug

• Related issues linked using fixes #number
• Integration tests added
• Errors have a helpful link attached, see contributing.md

Feature

• Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
• Related issues linked using fixes #number
• e2e tests added
• Documentation added
• Telemetry added. In case of a feature if it's used or not.
• Errors have a helpful link attached, see contributing.md

Documentation / Examples

• Make sure the linting passes by running pnpm build && pnpm lint
• The "examples guidelines" are followed from our contributing doc

[glasser]

Do I understand properly that this is a file used only on the server? Then I don't think we need this dependency on @apollo/client. I'd import gql from 'graphql-tag' directly instead (this is just a re-export), or honestly just define the schema as a string (perhaps read with fs.readFileSync from a schema.graphql file for better editor support) rather than parsing it with the gql tag.

[mjfwebb]

@glasser It is also imported indirectly, via the schema, by the Apollo client code in much the same way the existing Apollo examples do it.

Here's api-routes-apollo-server-and-client for example:

next.js/examples/api-routes-apollo-server-and-client/apollo/client.tsx

Lines 4 to 11 in ef2672d

	import { schema } from '../apollo/schema'
	import merge from 'deepmerge'
	let apolloClient
	function createIsomorphLink() {
	if (typeof window === 'undefined') {
	return new SchemaLink({ schema })

I'm not 100% confident we need to cover the windowless case here actually, so we could potentially update the client.

As an aside, do you know if the client file needs the .tsx extension, or does .ts suffice in this case with the only React code being useMemo?

[glasser]

Well, you can use graphql-tag directly in either case (and again, perhaps just a string?). But no huge deal I guess.

I'm not a client expert but I assume you only need .tsx if you're using JSX <> tags...