fix: top level ts-node registration bug

[Diizzayy]

Description

This PR simply averts from using a top level variable for the TypeScriptLoader to prevent the unnecessary early registration of ts-node

Related #8588

Type of change

• Bug fix (non-breaking change which fixes an issue)

[changeset-bot]

🦋 Changeset detected

Latest commit: 47282af

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

This PR includes changesets to release 2 packages

Name	Type
@graphql-codegen/cli	Minor
@graphql-cli/codegen	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

[charlypoly]

@Diizzayy, I've updated the changeset to minor since we use minor for breaking changes and major for big releases.

Besides that, I conducted some manual QA and did not found any regression, testing with the following config:

import { CodegenConfig } from "@graphql-codegen/cli";
import dotenv from "dotenv";
import { schemaPath } from "./test";

dotenv.config();

const config: CodegenConfig = {
  schema: schemaPath,
  documents: [process.env.DOCS!],
  generates: {
    "types.ts": {
      plugins: ["typescript", "typescript-operations"],
    },
  },
};

export default config;

Looks good to me, thanks! ⚡

[Diizzayy]

Besides that, I #8665 and did not found any regression, testing with the following config

@charlypoly Happy to hear! Thanks again for taking the time to have another look into this