chore(create-vite): move common ts settings to base tsconfig

[fmal]

Description

Discussed this briefly with @ArnaudBarre on Discord, this is a proposal to avoid duplication between tsconfigs.

Some Vite starter templates with typescript include tsconfig.json that references tsconfig.app.json and tsconfig.node.json. A lot of settings between app and node configs are repeated. This PR moves shared config props to root tsconfig.json and makes tsconfig.app.json and tsconfig.node.js inherit compilerOptions from it.

This works because references are excluded from inheritance (see https://www.typescriptlang.org/tsconfig/#extends)

[dominikg]

if this is motivated by DRY principles, i would ask to reconsider. Sharing compilerOptions between different config files that target different parts of an application should only be done because they are connected in that sense and you want to be able to have this file as a shared source of truth to prevent having to edit a compiler option in 2 places instead of one.

Creating a more complex extends chain is not only less tracable for human reading but also adds (a little) overhead to tsconfck for parsing these.

[dominikg]

Also keep in mind that these starters are intended to be a minimal starting point and carry little to no opinion and avoid complexity where possible.