[Bug]: `public_hoist_packages` does not fail repository setup if requested hash does not exist

### What happened?

Bad setup

Good Setup

We had a scenario where we were pinning a dep with `public_hoist_packages` and the packages ended up deduping in the lockfile. This meant that we no longer needed the hash. However, rules_js failed to catch that the hash'ed dep no longer existed and continued to build. This led to us having a binary go out that was missing a dependency and broke for some internal sites for end users.

The expected behavior should be if a requested dep from `public_hoist_packages` does not exist, it should fail the build and notify the user

### Version

Development (host) and target OS/architectures:

Output of `bazel --version`: 6.3.0

Version of the Aspect rules, or other relevant rules from your
`WORKSPACE` or `MODULE.bazel` file:

Language(s) and/or frameworks involved:
rules_js: `61616ef5e932c2ad5f76aefa2badcc700bca7e13`

### How to reproduce

```shell
See description above
```

### Any other information?

_No response_

Start by searching the repository for public_hoist_packages and the repository setup path, then reproduce the missing-hash case described in the issue. Done means setup fails with a user-facing error when a requested hash is absent, with regression coverage if the existing test structure supports it.

Written by the indexing model from the issue text.