mangleProps doesn't mangle TypeScript parameter property class field declaration

Nobody has claimed this yet.

When using a TypeScript parameter property together with `mangleProps`, esbuild 0.28.2 can rename the property access generated for the parameter property without renaming the corresponding class field declaration.

This results in two different property names being used for what should be the same property.

Is this expected behavior, or should the generated class field declaration participate in property mangling together with the corresponding property access?

## Reproduction

### Input

```ts
class MyClass {
constructor(public foo: null) {}
}

new MyClass(null);
```

### Building

```js
{
mangleProps: /^/
}
```

### Output

```js
class MyClass {
constructor(foo) {
this.a = foo;
}
foo;
}
new MyClass(null);
```

The `foo` parameter property is represented as a class field. However, `this.foo` is mangled to `this.a`, while the corresponding class field declaration remains `foo`. The generated code effectively contains two different properties, `a` and `foo`.

Start by running the TypeScript reproduction with mangleProps /^/ and compare the generated class field declaration with its property access. Done means the corresponding declaration and access use one consistent mangled property name, with behavior verified against the shown output.

Written by the indexing model from the issue text.