Attempt to fix webpack module resolution by renaming graphql.ts module

[benjamn]

May fix #8861, if my hunch is correct that webpack is resolving the 'graphql' in

import { isType } from 'graphql'

as importing from utilities/globals/graphql.ts module itself, rather than the graphql package, as suggested by the (possible exports: removeTemporaryGlobals) part of the error message:

WARNING in ./node_modules/@apollo/client/utilities/globals/graphql.js 4:4-10
export 'isType' (imported as 'isType') was not found in 'graphql' (possible exports: removeTemporaryGlobals)

The only relevant module that exports removeTemporaryGlobals is utilities/globals/graphql.ts, so renaming that module to something that cannot be confused with the graphql package should either fix the problem or at least shed more light on what's going on.

[benjamn]

Incredibly, this renaming fixes the reproduction provided in #8861. A pretty good guess, if I may say so myself!

[brainkim]

I don’t mind this being merged but the module resolution is just wrong and wonder if there is a deeper root cause which can be dealt with here or opened upstream.

[benjamn]

@brainkim Looks like this was a result of preferRelative: true in webpack.config.js: #8861 (comment)

From my perspective, the deeper root cause of this problem is that webpack's resolve.preferRelative setting should not apply to resolution of modules in node_modules. If there was a way to disable it (in, say, @apollo/client/package.json), that would be nice, but I haven't found a good way (for us) to do that yet.

[brainkim]

IMHO no one should ever be using that option and I am shocked that it exists.