build: use isolated declarations

[bluwy]

Description

Commits:

1. Update tsconfig files to enable isolatedDeclarations, and tweak the files/scripts to properly segment which files should enforce isolatedDeclarations. We don't want it for test files for example.
2. Ran https://github.com/microsoft/ts-fix. Ugly command but works:

ts-fix -t packages/vite/src/node/tsconfig.json -e 9007 -e 9008 -e 9009 -e 9010 -e 9011 -e 9012 -e 9013 -e 9014 -e 9015 -e 9016 -e 9017 -e 9018 -e 9019 -e 9020 -e 9021 -e 9022 -e 9023 -e 9024 -e 9025 -e 9026 --write --ignoreGitStatus
ts-fix -t packages/vite/src/module-runner/tsconfig.json -e 9007 -e 9008 -e 9009 -e 9010 -e 9011 -e 9012 -e 9013 -e 9014 -e 9015 -e 9016 -e 9017 -e 9018 -e 9019 -e 9020 -e 9021 -e 9022 -e 9023 -e 9024 -e 9025 -e 9026 --write --ignoreGitStatus
ts-fix -t packages/vite/src/shared/tsconfig.json -e 9007 -e 9008 -e 9009 -e 9010 -e 9011 -e 9012 -e 9013 -e 9014 -e 9015 -e 9016 -e 9017 -e 9018 -e 9019 -e 9020 -e 9021 -e 9022 -e 9023 -e 9024 -e 9025 -e 9026 --write --ignoreGitStatus
ts-fix -t packages/plugin-legacy/tsconfig.json -e 9007 -e 9008 -e 9009 -e 9010 -e 9011 -e 9012 -e 9013 -e 9014 -e 9015 -e 9016 -e 9017 -e 9018 -e 9019 -e 9020 -e 9021 -e 9022 -e 9023 -e 9024 -e 9025 -e 9026 --write --ignoreGitStatus

3. and rest of commits, fix formatting/linting and make the types look nicer.

[bluwy]

This and other similar setups are kinda funky to handle with isolated declarations, and they all relate to configDefaults, since our source code depends on satisifies and the inferred type. But it is an issue if we one day export configDefaults and its type, so the hoops here are as if we're tackling that now as isolated declarations don't know if the exported type is public

[sapphi-red]

How about this setting?

      '@typescript-eslint/consistent-generic-constructors': [
        'error',
        'type-annotation',
      ],

[bluwy]

Setting that has 101 errors. I think in some cases type-annotation makes sense for exported types with isolated declaration, but nested code that doesn't need it writes better if the type is in the constructor instead. Probably typescript-eslint needs a new option (or tweak constructor) that balances for isolated declarations.

[sapphi-red]

Makes sense. It seems typescript-eslint has languageOptions.parserOptions.isolatedDeclarations: true for that purpose.
https://github.com/typescript-eslint/typescript-eslint/pull/11351/files#diff-7ca46a3da27e8ad890168dc27f592c83d7f9e12334428396e11b8ca2a6a850adR52-R56

[bluwy]

Nice find! That option actually seems to work and we don't have to disable this rule