fix(vite): mask comments before scanning module export names - #11473

PR Checklist

• The PR title follows our guidelines.
• Issue filed: vite: extractDirectExportedNames matches 'export' inside comments, producing phantom CJS exports #11471
• CLA signed.
• All existing tests are passing — see testing note.
• Tests for the changes are included.

What is the current behavior?

extractDirectExportedNames scans module source for export declarations using regexes over raw text — comments are never masked. A CJS module containing a commented-out declaration such as

module.exports = {};
// export const roundRadiusProperty = {};

produces a phantom export name. Downstream, expandStarExports then emits

export { roundRadiusProperty } from "/ns/m/node_modules/ui-image/index-common.js";

which fails at link time on device because the served module never provides that binding (SyntaxError during HTTP-ESM instantiation; the boot aborts).

Same class of bug exists in scanModuleExportSurface's export */export {} from regexes and in extractExportMetadata, which scan raw text independently.

Real-world trigger: @nativescript-community/ui-image ships index-common.js with a commented-out // export const roundRadiusProperty = ... — any app depending on it can't boot a dev session.

What is the new behavior?

New maskJsComments helper blanks // and /* */ comment regions in-place while leaving string literals untouched (newlines preserved so match positions stay meaningful). Applied inside extractDirectExportedNames (the shared primitive) and at the top of scanModuleExportSurface and extractExportMetadata.

Fixes #11471.

Testing note

Added a regression spec in websocket-star-export-expansion.spec.ts — a star-export target carrying commented-out export lines no longer leaks the phantom name into the emitted import list. Verified locally via the bundled output (the workspace's full Nx setup wasn't available in my env). Minimal standalone repro: https://github.com/aleclarson/repro/tree/nativescript-11471