Remove rollup-plugin-ts

[ijlee2]

Description

This pull request downstreams the solution from embroider-build/addon-blueprint#136.

Migration guides

• Remove rollup-plugin-ts ember-container-query#203
• Remove rollup-plugin-ts embroider-css-modules#89

[ijlee2]

glint --declaration sets the compiler options declaration, emitDeclarationOnly, and noEmit (to true, true, and false, respectively) for the end-developer.

https://github.com/typed-ember/glint/blob/1.0.2/packages/core/src/cli/options.ts#L13-L16

For TS-only projects (i.e. without Glint), it is up to the end-developer to set these compiler options.

[ijlee2]

End-developers can somewhat simplify the lint:types script if they have 2 TS configuration files, one for development and another for production.

/* package.json for projects without Glint */
"scripts": {
  "build:types": "tsc",
  "lint:types": "tsc --project tsconfig.development.json",
  "start:types": "tsc --watch"
}

/* tsconfig.json */
{
  "extends": "@tsconfig/ember/tsconfig.json",
  "compilerOptions": {
    "declaration": true,
    "declarationDir": "declarations",
    "emitDeclarationOnly": true,
    "noEmit": false
  },
  "include": [
    "src/**/*",
    "unpublished-development-types/**/*"
  ]
}

/* tsconfig.development.json */
{
  "extends": "@tsconfig/ember/tsconfig.json",
  "compilerOptions": {
    "declaration": true,
    "declarationDir": "declarations"
  },
  "include": [
    "src/**/*",
    "unpublished-development-types/**/*"
  ]
}

Since it's not likely that a v1 addon had used a second configuration file such as tsconfig.development.json, I didn't think that the codemod should create this file for end-developers.