feat: explicit set useDefineForClassFields in ts templates

[sodatea]

Description

Since TypeScript 4.3, target: "esnext" indicates that
useDefineForClassFields: true as the new default.
See microsoft/TypeScript#42663

So I'm explicitly adding this field to the tsconfigs to avoid any
confusions.

Note that lit-element projects must use
useDefineForClassFields: false because of lit/lit#3278

Vue projects must use useDefineForClassFields: true so as to support
class style prop definition in vue-class-component:
vuejs/vue-class-component#465

Popular React state management library MobX requires it to be true:
https://mobx.js.org/installation.html#use-spec-compliant-transpilation-for-class-properties

Other frameworks seem to have no particular opinion on this.

So I turned it on in all templates except for the lit-element one.

Additional context

#4279 needs to be resolved before this PR to avoid confusing users.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes lit/lit-element#123).
• Ideally, include relevant tests that fail without this PR but pass with it.