Park TS/JS member calls whose receiver type lives in another repo (#3152) - #3387

Closes #3386. Continues #3152 (#3385 did Objective-C).

What changes

_resolve_typescript_member_calls now parks a member call whose receiver type is
declared nowhere in this build, instead of dropping it, and
link_cross_repo_member_calls finishes it once the graphs are composed.

Two commits, separable:

1. .mjs/.cjs activation. The resolver claimed .ts .tsx .mts .cts .js .jsx, so a
   pure-ESM corpus never ran type-aware member-call resolution at all. The suffix set is
   now one constant the resolver both activates on and parks by. Single-repo bug, has its
   own test that fails without the fix.
2. The parking. metadata.unresolved_calls on the caller (names only — no node ids,
   which the import edges silently dropped on Next.js codebase — short IDs vs full-path node IDs (regression of #256) #1529 remap and repo prefixing both rewrite), plus the "typescript" entry
   in _LANG_SUFFIXES.

The two precision calls, and why

Only table-typed receivers park. The resolver types a receiver either from the
per-file table (constructor parameter properties, local new bindings, bare
type_identifier annotations) or from spelling — an initial capital is taken to name the
type. That second arm is satisfied by import * as React, by default imports and by
plain const objects, and since node_modules is not scanned, most receivers that reach
the zero-declarations point through it are npm names. Parking them would send bare names
to the merge with nothing behind them, so the park is gated on not type_qualified.
test_a_namespace_style_receiver_is_not_parked pins it.

One _LANG_SUFFIXES key over all eight suffixes. A TS class legitimately answers a JS
call site, so splitting TS from JS would drop every TS↔JS cross-repo call.
test_a_typescript_call_binds_across_the_whole_js_family runs the four representative
suffixes.

The park is gated on a JS/TS suffix rather than a lang tag because TS raw_calls carry
no tag and this resolver iterates every language's — the same shape the Swift resolver
uses.

Interaction with the origin gate (#2553)

The gate runs after the single-definition check, so it only ever vets a name that did
match locally; the park sits at the zero-declarations point, strictly upstream and
disjoint. test_a_type_the_origin_gate_rejected_is_not_parked builds the gate's own case
(a local class Repo plus import type { Repo } from 'external-pkg') and asserts nothing
is parked, so a gate rejection cannot be laundered through the merge.

Known recall cost

interface_declaration, enum_declaration and type_alias_declaration all carry
_callable_class, so a type Greeter = ... alias in a third repo makes a genuine class
match ambiguous and the merge emits nothing. That fails closed, which is the bar the
existing resolvers set, and narrowing it belongs with whatever decides that a type alias
is not a call target.

Verification

• tests/test_cross_repo_member_calls.py + tests/test_ts_receiver_member_calls.py: 38 passed.
• Full suite: 5319 passed, 93 skipped, with tests/test_ollama_retry_cap.py deselected —
  its 4 failures reproduce unchanged on v8 at c9f9901.
• ruff check graphify tests: clean. Added lines are within 100 code points.