fix(extract): resolve TypeScript wildcard path aliases

[oleksii-tumanov]

Summary

• preserve and substitute single-wildcard compilerOptions.paths patterns
• prefer the longest matching wildcard prefix while retaining ordered target fallbacks
• add the requested regression coverage; barrel re-export changes remain out of scope

Scoped v8 follow-up to #927, which contains the original investigation and implementation. Related to #147.

Result

Relevant wildcard resolutions (path-normalized):

@communicate/documentv2  -> features/communicate/documentv2/src/index.ts
@communicate/interfaces  -> features/communicate/src/interfaces.ts
@/common/integration/foo -> preferred/foo.ts
@/feature/nested         -> generated/feature/shared/index.ts
app                       -> src/config/index.ts

The longest-prefix case emits no edge to fallback/common/integration/foo.ts.

Testing

• uv run --frozen --no-sync pytest tests/test_js_import_resolution.py -q (46 passed)
• uv run --frozen --no-sync pytest tests/ -q --tb=short (2517 passed, 28 skipped)
• uv run --frozen --no-sync ruff check graphify/extract.py tests/test_js_import_resolution.py (passed)

[safishamsi]

Merged into v8 (5746964) with your authorship. Thanks — clean extension of the #1531 _resolve_tsconfig_alias helper with proper single-* capture/substitution, longest-prefix/exact-wins specificity, baseUrl handling, and the ordered-fallback preserved. Verified the wildcard resolves end-to-end (incl. longest-prefix selection) with no false edges. Ships next release.