feature: detect inferred type cannot be named error

I was thinking about doing something similar.

Basically what's need is to get the package, install the dependencies, and see if the types in the output files can be resolved or not.

This is especially problematic with `pnpm` with monorepo as the transient packages are located at the top level `./node_modules/.pnpm/...`.

For example:

```sh
# Dependency graph
- lib-a
- lib-b
- lib-c
```

```sh
# folder
- packages
- lib-a
- node_modules
- lib-b # symlink to /node_modules/.pnpm/lib-b/version-y
- node_modules
- .pnpm
- lib-b@version-y
- lib-c@version-x
```

If `lib-b` does not re-exports the type from `lib-c`, you will get Inferred type cannot be named error.

The issue does not name files, tests, or an entry point. Start by tracing package installation and output-type resolution for pnpm monorepos, then define completion as detecting when an inferred type cannot be named because a transitive dependency's type is not re-exported.

Written by the indexing model from the issue text.