fix(transform): support import.meta.resolve in CJS

[lprnmns]

Problem

When an ESM-syntax JavaScript or TypeScript module is transformed to CommonJS by tsx, its synthesized import.meta object has no resolve function. A CJS entry that requires such a module therefore gets TypeError: define_import_meta_default.resolve is not a function. This reproduces the remaining gap described in #744.

Fix

Keep the existing synthesized metadata values and add a synchronous import.meta.resolve-compatible shim for CJS-transformed modules. Relative, absolute, URL, builtin, package-import, query, and conditional-export cases are covered by the URL path and Node resolver branches. A per-file collision-safe helper keeps user module bindings from shadowing the synthesized object. Native ESM transforms are unchanged.

Tests

• pnpm build — passed
• pnpm type-check — passed
• pnpm lint — passed with 0 errors (103 warnings)
• pnpm test — passed, 209 tests
• focused transform suite — 11 passed
• issue ESM required from CJS is missing import.meta props (works fine in Node 20) #744 CJS-to-ESM reproduction — exit 0; resolved URL printed

Compatibility

The change is limited to CJS transforms that contain import.meta. It does not add dependencies or change the lockfile. Bare package resolution uses Node's existing resolver with node/import conditions; the broader test suite passed on Node 24.15.0.

Related issue

Fixes #744