fix(graphql-language-service-server): run cache initialization once during startup

[lazerg]

Before the server is initialized, every file event goes through _loadConfigOrSkip, and nothing tracked an initialization that was already running. Events that arrived during a slow startup each started their own _initializeGraphQLCaches(). Each run swapped in a fresh GraphQLCache, so go-to-definition stayed unreliable until the last one finished.

This keeps the in-flight initialization promise and has later events await it instead of starting another run. It is cleared when the run settles, so a failed init can still be retried. Config reloads after startup and didChangeConfiguration work as before.

Fixes #4613

[changeset-bot]

🦋 Changeset detected

Latest commit: 74e3959

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

This PR includes changesets to release 1 package

Name	Type
graphql-language-service-server	Patch

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: lazerg / name: lazerg (74e3959)

[trevor-scheer]

Thanks for the PRs @lazerg, I have a busy couple weeks but I'll take a look when I'm able. In the meantime, please sign the CLA if you agree to it.

[lazerg]

Signed