build: move the build and test targets to @angular/build (#3807)

Angular CLI 22 deprecated the @angular-devkit/build-angular builders.
Both targets now use the @angular/build builders of the same names.
The specs run unchanged, now bundled by esbuild instead of webpack.

@angular/platform-browser-dynamic stays: @angular/platform-server/testing
imports it without declaring it. The lockfile is generated with npm 10,
which CI runs, because npm 11 drops entries npm 10 requires.

Author: armando-navarro

angular.json

@@ -10,14 +10,14 @@
 			"prefix": "angularfire",
 			"architect": {
 				"build": {
-					"builder": "@angular-devkit/build-angular:ng-packagr",
+					"builder": "@angular/build:ng-packagr",
 					"options": {
 						"tsConfig": "tsconfig.json",
 						"project": "src/ng-package.json"
 					}
 				},
 				"test": {
-					"builder": "@angular-devkit/build-angular:karma",
+					"builder": "@angular/build:karma",
 					"options": {
 						"polyfills": [
 							"zone.js",

karma.conf.js

@@ -25,15 +25,14 @@ if (process.env.FIRESTORE_EMULATOR_HOST &&
 module.exports = function (config) {
   config.set({
     basePath: '',
-    frameworks: ['jasmine', '@angular-devkit/build-angular'],
+    frameworks: ['jasmine'],
     plugins: [
       require('karma-jasmine'),
       require('karma-chrome-launcher'),
       require('karma-safarinative-launcher'),
       require('karma-firefox-launcher'),
       require('karma-jasmine-html-reporter'),
-      require('karma-coverage-istanbul-reporter'),
-      require('@angular-devkit/build-angular/plugins/karma')
+      require('karma-coverage-istanbul-reporter')
     ],
     client: {
       clearContext: false, // leave Jasmine Spec Runner output visible in browser