[Bug]: pnpm workspace projects with no `pkg` cause `rdeps` query failures

### What happened?

Some pnpm workspace projects have no `npm_package` target (the name defined by `npm_translate_lock(npm_package_target_name)`) because they are never linked into the package store. Projects such as "apps" are part of the pnpm workspace, have dependencies etc, but will most likely never be depended on so do not have `npm_package` targets. However it seems that target may still be referenced by a target generated by rules_js.

### Version

Language(s) and/or frameworks involved: ts+js

### How to reproduce

```shell
Declare a pnpm workspace, 2 projects, 1 project without an `npm_package`, then run an `rdeps` query such as:

bazel query 'rdeps(//...)'
```

### Any other information?

_No response_

Reproduce the pnpm workspace with two projects, including one without an npm_package target, then run the stated Bazel rdeps(//...) query. Trace the generated rules_js targets and the missing reference; done means the reverse-dependency query completes without failing on a nonexistent target.

Written by the indexing model from the issue text.