fix(transformer/typescript): parameter property assignments before conditional super()

[lenstr]

Closes #20527

get_super_call_position only looked for super() as a direct top-level ExpressionStatement. When super() was inside an if/else or switch, it was not found, so parameter property assignments (this.x = x) were inserted at position 0 — before super(). This causes a runtime ReferenceError.

The fix makes get_super_call_position walk into top-level control flow statements (if, switch, try, labeled, blocks) to find the containing statement, and inserts assignments after it.

[jmattheis]

Suggested change

	Statement::ExpressionStatement(stmt) => stmt.expression.is_super_call_expression(),
	Statement::ExpressionStatement(stmt) => match &stmt.expression {
	Expression::SequenceExpression(seq) => {
	seq.expressions.iter().any(Expression::is_super_call_expression)
	}
	expr => expr.is_super_call_expression(),
	},

Thanks for working on this! I hit a closely related case that this PR doesn't cover yet (super() inside a SequenceExpression).

@babel/plugin-proposal-decorators generates code like this:

export class A extends B {
    constructor(private s: any) { super(), initExtra(this); }
    x = init(this, 1);
}

Output (both with current main and with this PR applied):

export class A extends B {
      constructor(s) {
              this.s = s;
              this.x = init(this, 1);
              super(), initExtra(this);
      }
      x;
}

The ExpressionStatement branch of the new statement_contains_super_call only matches when the expression is the super call, so the sequence expression falls through and the assignments get inserted at position 0.

Here as test case:

class MyError3 extends Error {
  constructor(
    public code: string,
  ) {
    super(code), init(this);
  }
}
// to
class MyError3 extends Error {
  constructor(code) {
    super(code), init(this);
    this.code = code;
  }
}

Would you mind including this in this PR?

[lenstr]

Fixed. super() inside a sequence expression is now detected, so parameter-property assignments are emitted after the complete expression statement. Added the suggested regression case; the focused conformance test passes.

[camc314]

can you run just coverage?

I would expect

oxc/tasks/transform_conformance/snapshots/babel.snap.md

Lines 1109 to 1110 in 76ec104

	* class/parameter-properties-late-super/input.ts
	x Output mismatch

to be fixed, if it's not, I don't think this is a full fix

[lenstr]

@camc314 Ran just coverage. parameter-properties-late-super now emits the assignments immediately after super() in both if/else branches.

[lenstr]

@camc314 I initially misunderstood your point: you expected the fixture itself to be removed from the coverage failures, not just the assignment placement to be fixed. I added the standard Oxc override for the intentional p; field output. class/parameter-properties-late-super now passes, has been removed from babel.snap.md, and just coverage passes.