fix(extractor): capture static CommonJS imports and exports

[xiehuanyi]

Summary

Capture common top-level CommonJS require imports and named/default exports/module.exports assignments in the JavaScript and TypeScript structural extractor. Destructuring aliases/defaults, side-effect imports, static template paths, object barrels, and literal export keys are supported; dynamic paths, unrelated member calls, and shadowed CommonJS names are ignored. Node createRequire bridges from node:module/module remain recognized, including aliases and namespace imports. Mixed ES-module extraction is preserved, and the README explains the one-time fingerprint baseline change after upgrading.

Linked issue(s)

Closes #615. This fixes the direct extractor API, which still returned empty import/export arrays on current main; the import inventory improvements in #682 are preserved.

How I tested this

The issue's built TreeSitterPlugin.analyzeFile() reproduction changes from zero imports/exports to two imports and one deduplicated list export. The original 22 grammar-backed regressions include 18 failures on the original extractor and four passing negative controls. Fourteen additional JavaScript/TypeScript regressions cover shadowed require/module/exports and supported Node bridge forms, for 36 focused cases. The supplemental-import incremental fixture now uses a function-body dependency, retaining coverage for cosmetic edits while top-level requires correctly affect fingerprints.

• pnpm lint
• pnpm --filter @understand-anything/core test — 1,049 passing
• pnpm test — 786 passing, 12 skipped
• Core TypeScript build
• Built-package API reproduction

Inline assigned named functions currently produce an export entry without a function node; that remains a known limitation.

Versioning

• Version bumped to 2.9.8 in all six manifests listed in CLAUDE.md

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.