next.js

e5d0e38e - refactor(turbopack/next-{api,core}): Remove remaining uses of vc generics in non-test code (#70816)

refactor(turbopack/next-{api,core}): Remove remaining uses of vc generics in non-test code (#70816) After this change, `cargo check` on a branch that deletes vc generics support compiles successfully. ## Why? Rather than extended support for `Vc` generics to `ResolvedVc`, I plan to remove support for them entirely. That means fixing all the callsites (there's not many). Removing this is needed to get us to a point where 100% of structs can be `ResolvedValue`, because structs using these fields cannot otherwise be ported over to `ResolvedVc`. ## Okay, but Why? Explained here: https://github.com/vercel/turborepo/pull/8843#issuecomment-2253158412 I expect removing support for this will decrease the overall size of the codebase, as the logic for supporting generics is rather complicated.