fix(FR-2857): make pnpm install reliable under the minimumReleaseAge policy

- Enable `prefer-full-metadata=true` in `.npmrc` so pnpm fetches the
  registry `time` field. Without this, the existing `minimumReleaseAge`
  policy aborts `pnpm install` with `ERR_PNPM_MISSING_TIME` whenever a
  package's metadata is fetched fresh (abbreviated metadata omits `time`).
- Add `minimumReleaseAgeExclude` entries for `react@19.2.6` and
  `react-dom@19.2.6` (published 2026-05-06, less than 7 days before this
  change) so the recent React bump (#7330) is installable. Remove these
  entries once they age out on or after 2026-05-13.

Author: yomybaby

.npmrc

@@ -1 +1,7 @@
 # auth/registry overrides only — pnpm-specific settings live in pnpm-workspace.yaml
+
+# Request full registry metadata so the `time` field is available. pnpm v11's
+# `minimumReleaseAge` policy (set in pnpm-workspace.yaml) needs this field to
+# compute each version's age; without it `pnpm install` aborts with
+# ERR_PNPM_MISSING_TIME whenever a package's metadata is fetched fresh.
+prefer-full-metadata=true

pnpm-workspace.yaml

@@ -76,6 +76,12 @@ gitBranchLockfile: true
 
 minimumReleaseAge: 10080
 
+# Exclude packages that must be installable before they age out of the
+# `minimumReleaseAge` quarantine. Remove entries once they exceed 7 days.
+minimumReleaseAgeExclude:
+  - react@19.2.6
+  - react-dom@19.2.6
+
 allowBuilds:
   bufferutil: true
   core-js: true