fix: revert the lazy import of graphql

[grebenyuksv]

This reverts the recent attempts to import graphql lazily, which we agreed to do in #2250 (comment).

[kettanaito]

Thanks for opening this, @grebenyuksv. Can you please remind me what issue are you facing with the dynamic require?

I have a suspicion that merging this will cause errors for ESM consumers. Importing anything from the root results in an import to parseGraphQL, and then errors that the graphql package is not installed.

[kettanaito]

This looks great! Thank you, @grebenyuksv.

I confirm this is how it used to be before the lazy-loading disaster (ref).

[kettanaito]

I'm concerned that this change will make #2248 an issue again.

Perhaps we should take a closer look at why your use case errors, @grebenyuksv.

[grebenyuksv]

Thanks for your review, @kettanaito! Let's close it for now. I've parked that Storybook project where the dynamic import doesn't work and, as I said, I would rather bet that the problem is in other tooling, not in MSW.