fix(deploy): target Node 22 and the firebase-functions/v1 API in generated Cloud Functions

The generated function declared engines.node 14, a runtime Cloud
Functions decommissioned in early 2025, so it could not deploy at all.
The gen 1 template also called functions.region() on the
firebase-functions package root, which moved to the /v1 subpath in v6,
so a deployed function crashed at cold start with
TypeError: functions.region is not a function.

Node 22 is the newest runtime Cloud Functions supports and satisfies
the engines ranges of @angular/core and firebase-admin. Node 20 would
deploy today, but its security support ended 2026-04-30. The same
constant picks the Cloud Run base image, now node:22-slim. The docs
example moves off the decommissioned functionsNodeVersion 12.

Author: armando-navarro

docs/deploy/getting-started.md

@@ -97,7 +97,7 @@ Setting `functionsNodeVersion` and `functionsRuntimeOptions` in your `angular.js
 "deploy": {
     "builder": "@angular/fire:deploy",
     "options": {
-        "functionsNodeVersion": 12,
+        "functionsNodeVersion": 22,
         "functionsRuntimeOptions": {
           "memory": "2GB",
           "timeoutSeconds": 10,

src/schematics/deploy/functions-templates.ts

@@ -1,6 +1,9 @@
 import { DeployBuilderOptions } from './actions';
 
-export const DEFAULT_NODE_VERSION = 14;
+// Must be a runtime Cloud Functions still accepts, and must satisfy the engines of @angular/core
+// (the function runs the Angular server) and of firebase-admin. The `dockerfile` template below
+// also drops it into `FROM node:<version>-slim`, so it picks the base image on the Cloud Run path.
+export const DEFAULT_NODE_VERSION = 22;
 export const DEFAULT_FUNCTION_NAME = 'ssr';
 
 const DEFAULT_FUNCTION_REGION = 'us-central1';
@@ -34,7 +37,9 @@ export const defaultFunction = (
   path: string,
   options: DeployBuilderOptions,
   functionName: string|undefined,
-) => `const functions = require('firebase-functions');
+// `.region()` lives on the /v1 subpath since firebase-functions 6. Requiring the package root
+// instead still resolves, and fails only when the deployed function serves its first request.
+) => `const functions = require('firebase-functions/v1');
 
 // Increase readability in Cloud Logging
 require("firebase-functions/logger/compat");