next.js

df6cd599 - Turbopack: Remove `turbo_tasks::apply_effects`, use `Effects::apply` instead (#91858)

Turbopack: Remove `turbo_tasks::apply_effects`, use `Effects::apply` instead (#91858) Having both `apply_effects` and `Effects::apply` is confusing. `apply_effect`'s API seems a bit bad/dangerous because it combines work that should be done inside of a strongly-consistent operation (collecting the effects and reading their `Vc`s) with work that should be done at the top-level outside of any operation or turbo-task function (applying the effects). The first commit in this PR removes the `apply_effect` API and tries to improve documentation, including adding a doctest that compiles. The second commit in this PR is an LLM-driven refactor to remove the `apply_effect` callsites.