RFC: Re-expose the GraphQLSP TS plugin at gql.tada/ts-plugin

[kitten]

Summary

Currently, the Installation steps of gql.tada include installing @0no-co/graphqlsp and the explanations for how gql.tada functions differentiates between the two packages.

It may be a small detail, but this often forces us to refer to this project as gql.tada, by its package name, in the documentation, and to the TS LSP plugin as @0no-co/graphqlsp, which hinders being able to describe how this project functions in short and succinct ways.

Instead, we'd love to be able to automatically instally @0no-co/graphqlsp and not expose users to having to understand the internal workings of this structure.

Proposed Solution

We'd like @0no-co/graphqlsp to be re-exported as gql.tada/lsp (or a similar import).
This would mean that, in the future, the tsconfig.json changes would look as follows:

{
  "compilerOptions": {
    "strict": true,
    "plugins": [
      {
        "name": "gql.tada/lsp",
        "schema": "./schema.graphql",
        "tadaOutputLocation": "./src/graphql-env.d.ts"
      }
    ]
  }
}

No additional packages would be installed as @0no-co/graphqlsp would become a dependency of gql.tada and would be automatically installed.

This previously wasn't possible as TypeScript would block sub-paths from loading as a TS plugin, but will be enabled once this commit is released: microsoft/TypeScript@ef091bf

Requirements

• Re-export @0no-co/graphqlsp as gql.tada/lsp using the existing build pipeline

[kitten]

With 5.5 being in beta this is now unblocked: microsoft/TypeScript@ef091bf