fix(schematics): declare the runtime dependencies the schematics bundle requires (#3747)

The shipped schematics require jsonc-parser, @angular-devkit/core, and
@angular-devkit/architect at runtime, but the published manifest never
declared them. The first two resolve today only because npm hoists them
from the declared @angular-devkit/schematics and @schematics/angular.
Architect is worse: it is not in the package's dependency closure at
all and resolves from the app's own @angular/cli install, so ng deploy
breaks under pnpm's strict layout or Yarn PnP.

The architect range is the comparator pair matching its 0.YYMM version
scheme. A caret on a 0.x version would lock consumers to Angular 21.0.x.

Also prunes the ng-packagr allowlist to the seven names actually
declared, dropping ten entries for dependencies removed long ago and a
duplicate @schematics/angular.

Author: armando-navarro

src/ng-package.json

@@ -5,11 +5,8 @@
   },
   "dest": "../dist/packages-dist",
   "allowedNonPeerDependencies": [
+    "@angular-devkit/architect", "@angular-devkit/core",
     "@angular-devkit/schematics", "@schematics/angular",
-    "fuzzy", "inquirer-autocomplete-prompt",
-    "open", "jsonc-parser", "ora", "winston",
-    "triple-beam", "@schematics/angular", "node-fetch",
-    "semver", "inquirer", "fs-extra",
-    "firebase", "rxfire"
+    "jsonc-parser", "firebase", "rxfire"
   ]
 }

src/package.json

@@ -43,8 +43,11 @@
   "dependencies": {
     "firebase": "^12.4.0",
     "rxfire": "^6.2.0",
+    "@angular-devkit/architect": ">= 0.2100.0 < 0.2200.0",
+    "@angular-devkit/core": "^21.0.0",
     "@angular-devkit/schematics": "^21.0.0",
     "@schematics/angular": "^21.0.0",
+    "jsonc-parser": "^3.0.0",
     "tslib": "^2.3.0"
   },
   "ng-update": {