require-import fragment does not support module paths

[jksmithing]

Is your feature request related to a problem? Please describe.

In monorepos it's a common pattern to organize code across multiple internal packages.

Currently it's not possible to import a GQL fragment using a module path to an internal package, e.g. #import '@company/graphql/FooFields.gql'.

Describe the solution you'd like

I'd like to add support for module paths.

Describe alternatives you've considered

Relative paths: These work today but are not ergonomic or consistent with best practices for imports in JS/TS files. Further, we cannot utilize the mappings provided by the package.json exports field.

Additional context

N/A

[dimaMachina]

Hm, I never saw this pattern
https://github.com/jksmithing/graphql-eslint/blob/d33edb2dde1d8c6981bfb69907abb8010c3e2307/packages/plugin/__tests__/mocks/import-fragments/baz-fragment/package.json#L1-L3
, wdyt @dotansimha ?

Or was it just to make tests pass?