Plumb resolution through to eval config and output

[akhilles]

Note

Medium Risk
Touches core module loading/path resolution and propagates a new resolution/config object through eval, LSP, CLI, and tests, so regressions would primarily show up as broken load() resolution or stale caching across workspaces.

Overview
Evaluation now owns load resolution: EvalContextConfig stores file_provider, ResolutionResult, and a shared path_to_spec map, and EvalOutput carries the full config instead of a LoadResolver (removing CoreLoadResolver/LoadResolver APIs and updating all resolve_path/resolve_spec call sites).

Dependency resolution is promoted into core via a new ResolutionResult (with key canonicalization and package_closure), and workspace discovery now records a cache_dir via FileProvider::cache_dir; CLI/LSP/WASM code is refit to pass ResolutionResult into eval, cache resolutions per-workspace, and use resolution.workspace_info for file walking/vendoring/printing (print_dep_tree) and layout discovery call sites are adjusted accordingly.

^{Written by Cursor Bugbot for commit 1d51068. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}