Add support for module paths to require-import-fragment

[jksmithing]

Description

This change modifies the require-import-fragment rule to support module paths.

Fixes #2180

Type of change

• [x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Added a new test case to packages/plugin/__tests__/require-import-fragment.spec.ts.

Test Environment:

• OS: macOS 14.2.1
• @graphql-eslint/...: 4.0.0-alpha.0
• NodeJS: 18.12.1

Checklist:

• [x] I have followed the CONTRIBUTING doc and the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests and linter rules pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: d33edb2dde1d8c6981bfb69907abb8010c3e2307

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[frimmy]

@jksmithing niiice