RSC graphql duplicate import error

### Link to the code that reproduces this issue https://github.com/mjfwebb/nextjs-neo4j-graphql-error ### To Reproduce To reproduce the error just run the repository code with `npm run dev` and open http://localhost:3000/api/graphql in your browser. You will encounter an error thrown by graphql: ``` Error: Cannot use GraphQLNonNull "String!" from another module or realm. ``` To circumvent this error, we have to add the graphql package to `serverComponentsExternalPackages` in next.config.js (this is currently commented out). ### Current vs. Expected behavior I would expect this not to occur. This error can be circumvented using `serverComponentsExternalPackages` but it seems that graphql is a large enough library that it warrants being added to https://github.com/vercel/next.js/blob/canary/packages/next/src/lib/server-external-packages.json ### Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release ### Provide environment information ```bash Operating System: Platform: linux Arch: x64 Version: #50-Ubuntu SMP PREEMPT_DYNAMIC Mon Jul 10 18:24:29 UTC 2023 Binaries: Node: 20.0.0 npm: 9.6.4 Yarn: 1.22.18 pnpm: N/A Relevant Packages: next: 14.0.4-canary.25 eslint-config-next: 14.0.3 react: 18.2.0 react-dom: 18.2.0 typescript: 5.3.2 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) App Router, Middleware / Edge (API routes, runtime) ### Additional context _No response_