turbopack: ignore deferred circuit breaker cycles

[lukesandberg]

Summary

Export circuit breakers protect evaluation cycles by exposing lazy export getters before module execution. A cycle that closes only through a deferred module edge cannot be traversed during evaluation, so applying circuit-breaker code generation to it adds unnecessary early export setup and getters.

This change reuses the evaluation timing recorded on module-reference binding metadata when selecting circuit-breaker cycles. The cycle detector still considers only parallel, used edges, and now also excludes edges proven to execute after their parent module finishes evaluating. Deferred references remain in every reachability, export-usage, chunking, and runtime-loading path; only evaluation-cycle detection is narrowed.

Separate scope-hoisting fixtures pin both sides of the behavior: a cycle closed by a deferred require() uses normal bottom-of-factory value exports, while an all-eager cycle retains early getter initialization.

Verification

• cargo test -p turbopack-core module_graph --lib
• cargo nextest run -p turbopack-tests -E 'test(snapshot) | test(/circuit_breaker_(deferred|eager)_edge/) | test(/side_effect_optimization|side_effects_optimization/) | test(/async_modules/) | test(/execution__turbopack__scope_hoisting/) | test(/cjs_remove_unused_imports/)'
• cargo check -p turbopack-core -p turbopack-ecmascript -p turbopack-tests

[github-actions]

Tests Passed

Commit: fff8442