feat(js): add tree-shaking-based dependency narrowing to the JS project graph

[cw-alexcroteau]

Summary

This PR adds conservative tree-shaking-based dependency narrowing to the JS project graph.

It covers two related capabilities:

1. Static-graph narrowing: tree-shake projects out of the JS project graph when symbol-level analysis can prove the imported runtime symbols from a side-effect-free target are unused.
2. Affected narrowing: reduce the scope of affected-projects when a change only modifies some exported symbols and downstream projects do not import those symbols.

The affected-project narrowing is the higher-value part of the feature, because it directly improves affected precision for real code changes.

Current Behavior

1. When a project depends on another project via JS imports (i.e. an application importing a single symbol from a library), this creates a transitive relationship that can cascade into a lot of nested affected projects.
2. When affecting a project by changing some symbols in JS code, the all of the library's dependencies are considered affected even for projects that do not use the modified symbols.

Expected Behavior

1. Projects dependency graph is narrowed down based on imported symbols, especially for transient dependencies. If a project does not import symbols from other projects, it is excluded from the graph edges computation.
2. When affecting a project by changing some symbols in JS code, the modified library's dependencies should be considered as affected only if they use one or more of the modified symbols.

What This PR Does

In practice, that means:

• removing edges only when symbol-level analysis can prove the imported runtime symbols are unused
• keeping edges for side-effect imports, dynamic imports, namespace imports, re-exports, and other cases that cannot be narrowed safely
• applying the same conservative reasoning during affected calculation when only some exports in a file are modified

Public Reproduction

• repro PR: https://github.com/caseware/nx-node-tree-shake-graph-plugin/pull/9
• compat CI: https://github.com/caseware/nx-node-tree-shake-graph-plugin/actions/runs/26421260021

Related Context

• earlier core-port attempt: feat(js): add tree-shaken dependency narrowing to the JS project graph #35788

Related Issue(s)

Fixes #35797

[netlify]

👷 Deploy request for nx-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	8c15c27

[netlify]

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	8c15c27

[cw-alexcroteau]

@nrwl/nx-pipelines-reviewers I believe this is a sufficiently complex feature addition that warrants its own minor release for testing purposes, per the PR template. Please let me know if you believe the same.