[FR]: Add support for "injected" in "dependenciesMeta"

### What is the current behavior?

A dependency for which a `dependenciesMeta` entry exists will fail with an error like:

```
(21:34:32) ERROR: Traceback (most recent call last):
File "/Users/duarte.nunes/code/umani/BUILD.bazel", line 10, column 22, in
npm_link_all_packages(name = "node_modules")
File "/private/var/tmp/_bazel_duarte.nunes/f66c51e6a3394c97f40c1dcafe76e7fd/external/npm/defs.bzl", line 5548, column 27, in npm_link_all_packages
_npm_package_store(
Error in npm_package_store: npm_package_store rule '.aspect_rules_js/node_modules/@ui+amanara@0.0.0' in package '' conflicts with existing npm_package_store rule, defined at /Users/duarte.nunes/code/umani/BUILD.bazel:10:22
```

### Describe the feature

The motivation is to be able to correctly support peer dependencies for workspace packages: https://pnpm.io/package_json#dependenciesmetainjected.

Start with npm_link_all_packages and _npm_package_store in external/npm/defs.bzl, especially the conflict path shown in the report. Read pnpm's dependenciesMeta documentation and trace how injected workspace dependencies are represented. Done means dependenciesMeta entries using injected no longer cause the duplicate npm_package_store conflict.

Written by the indexing model from the issue text.