[api-extractor] Upgrade bundled TypeScript to 5.7

[colinaaa]

Summary

Fixes #4805

Details

TypeScript release notes:
https://devblogs.microsoft.com/typescript/announcing-typescript-5-5

1. Upgrade TypeScript to 5.5.2
2. Upgrade @typescript-eslint/parser to 7.14.1
3. Adopt breaking changes of typescript-eslint

How it was tested

Impacted documentation

[colinaaa]

@microsoft-github-policy-service agree

[colinaaa]

Hi @iclanton, I failed to solve the lint and build error of this change. Would you please help me with it? Thanks

[iclanton]

@colinaaa sure

[iclanton]

The issue is that the decoupled copies of the @rushstack/eslint-* packages are getting an old version of the @typescript-eslint/* packages. You should be able to fix this by patching those with the pnpm-config.json file or pnpmfile.

[FezVrasta]

Is there any plan to get this through?

[octogonz]

Fixes #5052

[octogonz]

The issue is that the decoupled copies of the @rushstack/eslint-* packages are getting an old version of the @typescript-eslint/* packages. You should be able to fix this by patching those with the pnpm-config.json file or pnpmfile.

@iclanton I have temporarily postponed these issues by upgrading API Extractor's TypeScript version to 5.7.2. while rollingback the other projects across the repo to version 5.4.2. In this way, the API Extractor work can be merged separately from the repo upgrade work.

The test projects are all building without errors, although there were warnings for the Heft's TypeScript 2.9.x test project. I didn't dig too deeply into that one -- since @types/node today only supports 3.2+, I think it's probably time to drop support for 2.9.x and make 3.2.x our oldest supported version. But we can do that in a separate PR as well.

[octogonz]

These projects were failing with a TypeScript 5.7.2 strict checks warning about resolve() signatures being inconsistent between @types/node/module.d.ts versus the compiler's lib.dom.d.ts:

Warning: C:/Git/rushstack/common/temp/default/node_modules/.pnpm/https://github.com/types+node@18.17.15/node_modules/@types/node/module.d.ts:210:13 - (TS2386) Overload signatures must all be optional or required.

The problem does not repro in @types/node@20 because the require() API is no longer experimental, however it does repro in the latest version of @types/node@18. This seems like an actual bug for @types/node@18 that will only repro for people who are (1) combining dom and node runtime targets (e.g. a web app with Jest), and also (2) are not shamefully setting skipLibCheck: true in their tsconfig.json.