Drop `ReferencedAsset::from_resolve_result` as a turbotask (#93297)
This task gets a lot of executions
```
Hit Rate Hits Misses Total Task Name
-----------------------------------------------------
74.0% 1,406,791 495,268 1,902,059 <turbopack_ecmascript::references::esm::base::EsmAssetReference as dyn turbopack_core::reference::ModuleReference>::resolve_reference
13.2% 64,134 423,084 487,218 <turbopack::ModuleAssetContext as dyn turbopack_core::context::AssetContext>::resolve_asset
29.3% 124,546 300,288 424,834 turbopack_core::resolve::resolve
86.4% 1,236,152 194,335 1,430,487 turbopack_ecmascript::references::esm::base::ReferencedAsset::from_resolve_result
```
However, the work being saved by those cache hits is very small and none
of the callers take advantage of 'cell identity' as no other turbo-tasks
take `Vc<ReferencedAsset>` as an input. So all we are doing is saving
the actual task execution which is a trivial read of the
`ModuleResolveResult`