fix(create-vite): use "target": "ES2020" in React template

[NMinhNguyen]

Description

Unless I am mistaken, I think this flag was unintentionally dropped in #12604 (cc @ArnaudBarre). This PR restores it for consistency with the other templates.

Additional context

---

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 PR Title 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 #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sapphi-red]

template-react-ts has "target": "ESNext", so useDefineForClassFields is enabled by default.

@ArnaudBarre I found other templates uses "target": "ES2020". Are there any reasons to use ESNext just for react? or is this just a mistake?

[ArnaudBarre]

This is clearly is mistake, it should be ES2020 (for lib, the others are mostly decorative given that this is configured in Vite) + useDefineForClassFields

[NMinhNguyen]

template-react-ts has "target": "ESNext", so useDefineForClassFields is enabled by default.

Ah my bad 😅

[NMinhNguyen]

This is clearly is mistake, it should be ES2020 (for lib, the others are mostly decorative given that this is configured in Vite) + useDefineForClassFields

Wait, so target should remain as ESNext?

[ArnaudBarre]

Yeah "module" doesn't bring much and Vite will jump on the new features when they arrive for that so I think this good like this

[sapphi-red]

Thanks for updating!