next.js

14c1f8c6 - Turbopack: Use `std::any::type_name` for global naming of turbo-task items (#89874)

Turbopack: Use `std::any::type_name` for global naming of turbo-task items (#89874) _I wrote this PR by hand, because I wanted to make sure I got all the details right._ The previous approach for computing global names was `module path` + `item name`. Since @lukesandberg added support for inventory, we can now nest `turbo_task::function` and `turbo_task::value` macros inside any arbitrary scope:  This is a fantastic feature, but it does mean that our global names are no longer unique. @mmastrac suggested using `std::any::type_name` with a dummy marker type to get a full path. This PR attempts to do that.