…denciesMeta from the registry

`PackageVersion` (the per-version registry manifest the npm resolver
parses) was missing the `optionalDependencies` and `peerDependenciesMeta`
fields. The resolver builds `ResolveResult.manifest` via
`serde_json::to_value(picked)` and downstream walks it with
`extract_children` (reads `optionalDependencies`) and
`extract_peer_dependencies` (reads `peerDependenciesMeta`). Without
those fields on the struct, both reads always saw nothing — so
`optionalDependencies` edges were silently dropped, and every optional
peer was treated as required, then auto-installed via the
`autoInstallPeers` fallback in `hoist_peers`.

On the vlt astro fixture this cascaded badly: `unstorage`'s 19 optional
peers (`@azure/*`, `@vercel/*`, `@netlify/blobs`, `@upstash/redis`, ...)
got auto-installed and pulled in their transitive deps, while astro's
own `optionalDependencies` (`sharp`) was missing entirely. Pacquet's
lockfile carried 1535 resolutions vs pnpm's 377 — the "5.5x astro
deep-tree slowdown" tracked in #11902 was almost all wasted work, not a
real perf bug.

After this patch on the vlt astro fixture:

- `pacquet install` warm-store: 39.6s -> 8.5s (4.7x), now within 22% of
  pnpm.
- Lockfile: 13364 lines -> 3037 lines (pnpm: 3444).
- Resolutions: 1535 -> 377 (matches pnpm exactly).
- Astro root peer suffixes: 30 (azure/vercel/...) -> `(rollup@4.60.4)(typescript@5.9.3)` (matches pnpm).
- `sharp` correctly installed via astro's `optionalDependencies`.
- Warm-cache hyperfine (3 runs): pacquet 670ms +/- 72ms vs pnpm 1.27s
  +/- 7ms — pacquet 1.89x faster.

Added a regression test that deserializes a fixture with both fields
populated and asserts they round-trip through `serde_json::to_value`,
which is what the resolver consumes.

---
Written by an agent (Claude Code, claude-opus-4-7).

…nciesMeta

Port the upstream test cases that exercise the same correctness concern
the previous commit fixed — `optionalDependencies` and
`peerDependenciesMeta` round-tripping through the resolver and the
bundled-manifest pipelines.

Tests added:

- `pacquet-resolving-npm-resolver::npm_resolver::tests::resolved_manifest_carries_optional_dependencies_and_peer_dependencies_meta` —
  mocks a registry packument that declares both fields and asserts the
  resolver-produced `ResolveResult.manifest` carries them as
  camelCase JSON keys. This is the tightest level at which the
  #11934 bug surfaces: before the fix, `serde_json::to_value(picked)`
  dropped both fields because `PackageVersion` didn't declare them.

- `pacquet-package-manager::install::tests::auto_install_peers_does_not_cascade_optional_peers` —
  ported from upstream's "warning is not reported when cannot resolve
  optional peer dependency" at
  https://github.com/pnpm/pnpm/blob/1fb8a2d5d8/installing/deps-installer/test/install/peerDependencies.ts#L1181-L1255.
  Installs `@pnpm.e2e/abc-optional-peers@1.0.0` against the real mock
  registry under default `autoInstallPeers: true`; asserts that the
  required peer (`peer-a`) lands in the virtual store while the two
  optional peers (`peer-b`, `peer-c`) stay out. Before the fix,
  `peerDependenciesMeta` was dropped and the `autoInstallPeers`
  fallback in `hoist_peers` cascaded both optional peers (plus their
  transitives) into the install.

- `pacquet-package-manager::install::tests::auto_install_peers_skips_meta_only_optional_peers` —
  ported from upstream's companion test
  https://github.com/pnpm/pnpm/blob/1fb8a2d5d8/installing/deps-installer/test/install/peerDependencies.ts#L1257-L1323.
  Same assertion shape but the optional peers are declared *only* via
  `peerDependenciesMeta` (no matching `peerDependencies` entry);
  upstream and pacquet treat such entries as optional peers with an
  implicit range of `*`.

- `pacquet-tarball::tests::normalize_bundled_manifest_tests` (8 cases) —
  ported from upstream's
  https://github.com/pnpm/pnpm/blob/1fb8a2d5d8/store/cafs/test/normalizeBundledManifest.test.ts.
  The bundled-manifest pipeline is the install-side sibling of the
  resolver-side path the previous commit fixed; pacquet's
  `normalize_bundled_manifest` already preserves the right fields,
  but had zero unit tests. Pins the field-preservation contract so a
  regression there can't replicate #11934 on the install
  side. Two upstream cases are intentionally not ported (semver.clean
  normalization and the `0.0.0` default for missing versions) because
  pacquet's port intentionally diverges from upstream on both, per the
  function's existing doc comment.

---
Written by an agent (Claude Code, claude-opus-4-7).

- `pacquet-tarball::tests::normalize_bundled_manifest_tests::preserves_optional_dependencies_and_peer_dependencies_meta_keys`
  had a trailing comma on a single-line `assert_eq!` invocation that
  `cargo fmt` left in place; `perfectionist::macro-trailing-comma`
  rejects it under `-D warnings`. Drop the comma.
- Trim the rustdoc + inline comments on
  `auto_install_peers_does_not_cascade_optional_peers` down to the
  regression intent + upstream link; the assertions themselves carry
  the mechanics.

---
Written by an agent (Claude Code, claude-opus-4-7).