Add require-import-fragment rule

[FloEdelmann]

Description

Fixes #1413

Type of change

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

How Has This Been Tested?

Via unit tests (see changed files).

Test Environment:

• OS: Ubuntu 22.04
• NodeJS: 16.19.0

Checklist:

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

[changeset-bot]

🦋 Changeset detected

Latest commit: 007cbf3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@graphql-eslint/eslint-plugin	Minor

Not sure what this means? Click here to learn what changesets are.

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

[dimaMachina]

also, what will happen if you import not-foo.graphql and this file does not contain Foo fragment

# import Foo from 'not-foo.graphql'

        query MyQuery {
          fooField {
            ...Foo
          }
        }

[FloEdelmann]

That looks really good, thank you!

[FloEdelmann]

Why .name and not just Name?

[dimaMachina]

it is because FragmentDefinition Name will match

// some abstract GraphQL AST Node
const node = {
  type: 'FragmentDefinition',
  name: { // ✅ matched 1
    type: 'Name'
    // ...
  },
  foo: { // ✅ matched 2
    type: 'Name',
    bar: { // ✅ matched 3
      type: 'Name' 
      // ...
    }
    // ...
  }
  // ...
}

2. FragmentDefinition .name will match only node.name
3. FragmentDefinition > Name will match only node.name and node.foo but not not.foo.bar

So for more safety, it should be FragmentDefinition > .name, I remember I got some issue due too wide selector, so it's better to be explicit while selecting nodes

[dimaMachina]

thanks for working on it! In case you would work on other rules you could extract some pieces of code for parsing#import comments!