build: do not auto install peer dependencies

Avoid pnpm auto-installing peer dependencies. We want to be explicit about our versions used
for peer dependencies, avoiding potential mismatches. In addition, it ensures we can continue
to rely on peer dependency placeholders substituted via Bazel.

Author: devversion

.aspect/rules/external_repository_action_cache/npm_translate_lock_MzA5NzUwNzMx

@@ -1,7 +1,7 @@
 # @generated
 # Input hashes for repository rule npm_translate_lock(name = "npm2", pnpm_lock = "@//:pnpm-lock.yaml").
 # This file should be checked into version control along with the pnpm-lock.yaml file.
-.npmrc=-2023857461
+.npmrc=-1406867100
 package.json=688000741
 packages/angular/cli/package.json=349838588
 packages/angular/pwa/package.json=-1352285148
@@ -13,6 +13,6 @@ packages/angular_devkit/schematics/package.json=673943597
 packages/angular_devkit/schematics_cli/package.json=-356386813
 packages/ngtools/webpack/package.json=-942726894
 packages/schematics/angular/package.json=251715148
-pnpm-lock.yaml=926343104
+pnpm-lock.yaml=604009520
 pnpm-workspace.yaml=1732591250
 yarn.lock=969972397

.npmrc

@@ -5,3 +5,8 @@ engine-strict = false
 # projects using rules_js so that pnpm outside of Bazel lays out a node_modules tree similar to what
 # rules_js lays out under Bazel (without a hidden node_modules/.pnpm/node_modules)
 hoist=false
+
+# Avoid pnpm auto-installing peer dependencies. We want to be explicit about our versions used
+# for peer dependencies, avoiding potential mismatches. In addition, it ensures we can continue
+# to rely on peer dependency placeholders substituted via Bazel.
+auto-install-peers=false