Wrong lint results when running lint after moving fragment declaration to another file

[lwasyl]

Issue looks very similar to #1232. I"m running eslint.lintFiles("Queries") repeatedly on a changing set of graphql files. It seems that when a fragment is moved from one file to another between runs, the subsequent runs fail e.g. unknown fragment check.

It looks like the following line keeps a global cache which affects subsequent runs: https://github.com/dimaMachina/graphql-eslint/blob/master/packages/plugin/src/siblings.ts#L29

Is there any way to reset that cache?

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

• 1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox

  For example, you can start off by editng the
  'basic' example on Stackblitz.

  Please make sure the graphql-eslint version under package.json matches yours.

• 2. A failing test has been provided

• 3. A local solution has been provided

• 4. A pull request is pending review

---

Describe the bug

To Reproduce Steps to reproduce the behavior:

Expected behavior

Environment:

• OS:
• @graphql-eslint/eslint-plugin:
• Node.js:

Additional context

[jaydenseric]

Might be related to #2511 ?