Starting in TypeScript 5.6, `.tsbuildinfo` file is always written in a
`--build` invocation[^1].
So the entire community need to embrace the new behavior and explicitly
set `tsbuildInfoFile` if they want to avoid polluting the project root.

So I think it's no longer our responsibility to find a workaround for
the users.

Closes #27

[^1]: https://devblogs.microsoft.com/typescript/announcing-typescript-5-6-beta/#tsbuildinfo-is-always-written

We've enabled `noEmit` for a while and the constraint on solution-style
tsconfigs were no longer a problem long ago. So let's enable it.

It's considered a good practice as illustrated in:
https://www.totaltypescript.com/cannot-redeclare-block-scoped-variable#solution-3-your-module-isnt-a-module

While the configuration options are not case-sensitive, it is good to
keep the casing consistent.
The JSON schema at https://json.schemastore.org/tsconfig uses `Bundler`,
so we should use the same casing.

Because `jsxImportSource: "vue"` is only available in Vue 3.3 and above:
<https://blog.vuejs.org/posts/vue-3-3#jsx-import-source-support>

I also made both `vue` and `typescript` optional peer dependencies,
in case the configuration is not used to *run* or *type-check* a vue
project, but only to *transpile* some source code.

Closes #17, as we never intended to support Vue 2.x in the first place,
even it works in some earlier versions, the configuration might not be
optimal for Vue 2.x projects.

BREAKING CHANGE:
This change requires libraries extending `tsconfig.lib.json` to be
type-checked against their dependencies as well as the `.d.ts`
files in their own projects. So it might introduce new type errors.

It bumps the Vue.js version requirement to `^3.4.0`, as the Vue.js core
can only be correctly type-checked in `--isolatedModules` mode after
version 3.4 (following the removal of `const enum` usage).

It might also increase the compilation time of the library projects.