Apply the no-star-imports guideline added in #364:

> Avoid star (glob) imports inside the bodies of regular modules.
> Import items explicitly by name everywhere except external-crate
> preludes and root-of-module re-exports.

The only star inside the new module's body was `use super::*;` in
`crates/modules-yaml/src/edge_cases.rs`. Listed the four helpers the
file actually uses (`derive_hoisted_dependencies`,
`drop_empty_hoist_fields`, `is_empty_or_null`, `sort_skipped`) so a
future stale import here surfaces as an unused-import warning.

Apply the "No star imports" rule from CODE_STYLE_GUIDE.md (added by
PR #364) to the test modules introduced by this PR. Each test module
now imports its parent's items by name instead of via the glob, so a
removed parent item is caught by the compiler instead of silently
shadowing an unrelated re-export.

Affected:

* crates/cmd-shim/src/bin_resolver/tests.rs
* crates/cmd-shim/src/link_bins/tests.rs
* crates/cmd-shim/src/shim/tests.rs
* crates/package-manager/src/link_bins/tests.rs
* crates/package-manager/src/symlink_direct_dependencies/tests.rs

The four `pub use submodule::*;` re-exports in `crates/cmd-shim/src/lib.rs`
stay as-is — those are the root-of-module re-export form the guide
explicitly allows.

PR #364's narrowed test imports in `crates/package-manager/src/install.rs`
left out the symbols that the stage-event smoke test from PR #349
references (`LogEvent`, `Reporter`, `Stage`, `StageLog`, plus
`Lockfile`). The test module compiles cleanly with `--tests` enabled
once the imports are restored — without this, `cargo check --tests`
fails on the merged main even before this branch's changes are applied.

Found while applying PR #364's "No star imports" rule to my own test
files; surfacing the fix here instead of leaving main red.

Follow the new "No star imports" rule from #364 across the test
modules in this PR's new and modified files: `crates/network/src/auth.rs`,
`crates/npmrc/src/env_replace.rs`, `crates/npmrc/src/lib.rs`,
`crates/npmrc/src/npmrc_auth.rs`, `crates/registry/src/package.rs`,
`crates/registry/src/package_version.rs`, and
`crates/tarball/src/tests.rs`. Each `use super::*;` is replaced
with the minimal set of names the test bodies actually reference;
intra-doc links to other module-private items resolve without an
import.

…action

The unit-test module in `crates/package-manager/src/install.rs` was
left referencing five symbols not in scope after PRs #349
and #364 landed on main in succession. #349 added a test
that uses `Lockfile`, `Reporter`, `LogEvent`, `StageLog`, and `Stage`;
#364 (no star imports) replaced the previous `use super::*;` with
`use super::{Install, InstallError};` and didn't carry over the
additional symbols the new test needed. The result is `cargo test
-p pacquet-package-manager --lib` failing to compile on `main` itself
across all three CI platforms.

Restore the missing items by name in the test imports so the
no-star-imports rule still holds:

    use pacquet_lockfile::Lockfile;
    use pacquet_reporter::{LogEvent, Reporter, SilentReporter, Stage, StageLog};

Verified pre-existing on `origin/main` (`git switch --detach
origin/main && cargo build --tests -p pacquet-package-manager`
produces the same nine errors). Per AGENTS.md ("If a test was already
broken on main, fix it as part of your work"), fixing here.

…370)

#364's `use super::*;` removal stripped the test module's view of
`LogEvent`, `Reporter`, `Stage`, `StageLog`, and `Lockfile`, but the
test bodies still reference them — so `cargo nextest run -p
pacquet-package-manager` failed to compile on `main`.

Promote the inline `use pacquet_lockfile::Lockfile` from
`frozen_lockfile_flag_overrides_config_lockfile_false` to the module-
level `use` block, and add the missing reporter symbols alongside the
existing `SilentReporter` import. The two `Lockfile`-using tests now
share one import.

The no-star-imports sweep in #364 dropped symbols the reporter
smoke test in #349 needs. `crates/package-manager/src/install.rs::tests`
references `Stage`, `LogEvent`, `Reporter`, `StageLog`, and `Lockfile`
in its body, but the explicit-import list only kept `Install` and
`InstallError`. Restore the missing names so the crate compiles.

Confirmed pre-existing on `origin/main` (`cargo check --tests
-p pacquet-package-manager` reproduces). Same drive-by fix is in
flight as part of #332. Picking it up here so this PR's CI is not
blocked by the upstream regression.