Fix CommonJS export destructuring emit

[jakebailey]

Fixes #4403

[Copilot]

Pull request overview

Adds regression coverage (and a small transformer fix) for a CommonJS emit bug where module-scope export const { … } = <importedValue> could lose the import namespace qualification on the RHS, leading to a runtime ReferenceError at module load (Fixes #4403).

Changes:

• Fix CommonJS module transformer ancestor tracking when converting exported binding-pattern variable declarations into destructuring assignments.
• Add a compiler repro test covering exported destructuring from imported values under --module commonjs (including array/object patterns, aliasing, default import, and default initializers).
• Add an additional compiler test ensuring namespace-export destructuring preserves correct qualified references inside the namespace.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
internal/transformers/moduletransforms/commonjsmodule.go	Push/pop ancestor stack around synthesized destructuring assignment so identifier reference substitution (imports/exports) runs with the correct parent context.
testdata/tests/cases/compiler/commonjsExportDestructuringImportedValue.ts	New regression test for CommonJS emit of export const {…} = importedValue (and related destructuring cases).
testdata/baselines/reference/compiler/commonjsExportDestructuringImportedValue.js	Baseline validating RHS stays qualified (e.g. enum_1.CodePriceType) in emitted CommonJS output.
testdata/tests/cases/compiler/namespaceExportDestructuringReferences.ts	New test ensuring namespace export destructuring uses the namespace-qualified references for computed names and default initializers.
testdata/baselines/reference/compiler/namespaceExportDestructuringReferences.js	Baseline validating correct namespace-qualified emit (N.key, N.fallback, etc.).