Prior to this commit, if `symlink` was set to `false` (such as in an RC
file), `dlx` would throw `ENOENT` because it expected the
`node_modules/the-package` symlink to exist:
```console
$ pnpm config get symlink
false
$ rm -rf ~/.cache/pnpm/
$ pnpm dlx the-package
Packages: +1
+
Progress: resolved 1, reused 1, downloaded 0, added 1, done
ENOENT ENOENT: no such file or directory, open '/home/${USER}/.cache/pnpm/dlx/.../
node_modules/the-package/package.json'
```
This commit filters the `symlink` option before installing the package,
allowing the symlink to be created, preventing the error.
Fixes#8732.
* fix(dlx/cache): account for customized registries
Different registries potentially return different packages for the same
name, so reusing dlx cache for packages from a different registry would
be incorrect.
* style: eslint
* refactor: dlx
---------
Co-authored-by: Zoltan Kochan <z@kochan.io>
