fix: handle multiple tsconfig extends for resolving GraphQLSP plugin entry

[aweber1]

Summary

Given the following tsconfig.json setup:

// tsconfig.json
{
  "extends": ["./tsconfig.app.json", "./tsconfig.gql-tada.json"]
}

// tsconfig.app.json
{
  "compilerOptions": {
     // some options here
   }
}

// tsconfig.gql-tada.json
{
  "compilerOptions": {
    "plugins": [
      {
        "name": "gql.tada/ts-plugin",
        // schema config
      }
    ]
  }
}

I encounter the following error:
Could not find a valid GraphQLSP plugin entry in: tsconfig.json

The code in this PR fixes the issue for me, but there aren't unit tests specifically for this area of code so not sure of any adverse effects.

Set of changes

The change was pretty straightforward in just modifying return load(tsconfigPath) to be return await load(tsconfigPath) so that exceptions thrown when trying to load nested tsconfig "extends" elements are caught (and swallowed) by the intended catch(_error) statements.

[changeset-bot]

🦋 Changeset detected

Latest commit: f216c49

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

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

[kitten]

Nice catch! didn't spot this typo when refactoring this file. I think this must've regressed when this was made more reusable