Built-in tool tasks miss the cache after the workspace moves #790

Problem

When a task runs a built-in tool like vp lint or vp test, the planned command includes the absolute path of the tool's entry script, for example /home/me/project/node_modules/oxlint/bin/oxlint. That path is part of the cache key, so moving the workspace, cloning it somewhere else, or running from a git worktree misses the cache for every one of those tasks, even though nothing about them changed.

Proposal

Let the code that synthesizes these commands pass the tool's entry script separately from its other arguments. When the entry is inside the workspace, vp run passes it relative to the task's directory, in both the command it runs and the cache key. Everything else stays as it is today.

Related

#717 covers the case where the entry is outside the workspace, in a global pnpm store. That needs a different fix.