fix(compile): namespace import of CJS default re-export resolves member value (#4841)

[proggeramlug]

Summary

Fixes #4841 — Stripe SDK stripe.products.create({ name }) threw TypeError: replace is not a function on every request.

Root cause

import * as qs from "qs" then qs.stringify(data, opts).replace(/%5B/g, "[") (Stripe's utils.js). qs.stringify(...) returned the qs stringify function instead of a string, so .replace was undefined.

The real bug is in import * as ns namespace-member resolution. qs/lib/index.js is CommonJS:

var stringify = require('./stringify');   // ./stringify is `module.exports = function(...)`
module.exports = { formats, parse, stringify };

The submodule records its export under the synthetic "default" suffix, not the consumer-visible member name stringify. The namespace-import var-vs-function classifier keyed only on (origin_path, "stringify"), missed the (origin_path, "default") entry, and classified stringify as a function. That routed ns.stringify through the singleton-closure wrap of the default getter, so ns.stringify(args) returned the function value instead of being it (typeof ns.stringify(...) === "function", .length === 0).

The default import (import qs from "qs"; qs.stringify) worked because it reads module.exports.stringify directly — only the import * as namespace path was broken.

Minimal repro:

// node_modules/mini/index.js : var sfy = require('./sfy'); module.exports = { sfy };
// node_modules/mini/sfy.js   : module.exports = function (o) { return "S:" + o; };
import * as m from "mini";
(m as any).sfy("X");   // before: returns a function (len 0); after: "S:X"

Fix

The namespace arm in compile.rs now probes both (origin_path, member) and (origin_path, origin_name) against exported_var_names, mirroring the existing named-import arm (the origin_key_under_origin_name dual-probe). With the member correctly classified as a var, ns.stringify reads the getter's value.

One-arm change + an e2e regression test.

Verification

Built on Linux x86_64 (where the bug reproduced) and ran the real Stripe SDK repro:

• Before: ERR: TypeError replace is not a function
• After: stripe.products.create({ name }) builds and dispatches the request, reaching Stripe's API (the request layer is no longer broken).
• qs.stringify({a:1,b:"x"}) → "a=1&b=x" (was the function value).

The remaining "unsettled top-level await" when awaiting the real network call is a separate, pre-existing async-HTTP-settling issue (already noted in #4841 as out of scope) — identical on macOS, and unrelated to the .replace failure this PR fixes.

Regression-checked normal namespace imports (real function/const exports, default imports) and the existing issue_4858 / native_link_cache integration tests — all green.