fix(esbuild): fix static properties transpile when useDefineForClassFields false

[bluwy]

Description

Fix #13863

In esbuild 0.18, when target: 'esnext' is passed, and useDefineForClassFields is false, it transpiles

class Foo {
  static bar = 'hello'
}

into

class Foo {
  static {
    bar = 'hello'
  }
}

Which the latter support isn't great, but it's because we specify esnext that it transpile it that way. In this PR, I disabled this static block transpilation so it transpiles to a syntax that's better supported:

class Foo {}
Foo.bar = 'hello'

Additional context

I don't think this is a great fix. I've noted something we can improve on in the TODO to not rely on esnext by default.

---

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.