fix(esbuild): use useDefineForClassFields: false when no compilerOptions.target is declared

[sapphi-red]

Description

esbuild seems to use useDefineForClassFields: true when target isn't declared in tsconfig. (TypeScript uses useDefineForClassFields: false in that case)
https://esbuild.github.io/try/#dAAwLjE4LjExAC0tbG9hZGVyPXRzICctLXRzY29uZmlnLXJhdz17ImNvbXBpbGVyT3B0aW9ucyI6e319JwBjbGFzcyBGb28gewogIGZvbyA9ICdmb28nCn0

refs #13525

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.

[patak-dev]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
analogjs	✅ success
astro	✅ success
histoire	❌ failure
iles	❌ failure
ladle	✅ success
laravel	✅ success
marko	✅ success
nuxt	✅ success
nx	✅ success
previewjs	✅ success
qwik	✅ success
rakkas	✅ success
sveltekit	✅ success
unocss	❌ failure
vite-plugin-pwa	✅ success
vite-plugin-ssr	✅ success
vite-plugin-react	✅ success
vite-plugin-react-pages	✅ success
vite-plugin-react-swc	✅ success
vite-plugin-svelte	✅ success
vite-plugin-vue	❌ failure
vite-setup-catalogue	✅ success
vitepress	✅ success
vitest	✅ success