same short name used for import and for class

```js
import * as e from '@angular/core'; // module scope: e = Angular core namespace

let e$1 = class e { // named class expression: inner `e` = the class
static {
this.ɵprov = e.ɵɵdefineInjectable(...) // `e` here is the CLASS, not Angular core → TypeError!
}
}
```

Start from the JavaScript reproduction in the issue and trace esbuild's handling of the import namespace and named class-expression bindings. Confirm the transformed output keeps the two short names distinct and no longer produces the reported TypeError when the static block runs.

Written by the indexing model from the issue text.