docs: cover ng update stopping on a Node.js version message (#3788)

* docs: cover ng update stopping on a Node.js version message

`ng update @angular/fire@next` can stop with "The Angular CLI requires
a minimum Node.js version of ..." on a Node.js version that Angular 21
supports. `ng update` runs with the newest Angular CLI when the first
@angular/ package in the command has no version number, and that CLI
requires a newer Node.js than Angular 21 does.

The example gives the full release-candidate version because
`@angular/fire@21` matches nothing until 21.0.0 is published.

Fixes #3786

* docs: name both ng update forms in the Node.js version note

`ng update @angular/fire@21` matches nothing until 21.0.0 is
published, so the note gave only the release-candidate form and
would have needed an edit at the release. It now gives both.

Author: armando-navarro

docs/version-21-upgrade.md

@@ -82,3 +82,4 @@ Two symbols were removed rather than renamed. The migration leaves their imports
 
 - **Angular 21.2 is required.** AngularFire 21 peers `@angular/* ^21.2.0` and does not support Angular 22 (a future AngularFire 22 will).
 - The obsolete `@angular/platform-browser-dynamic` peer dependency was removed. No action is needed.
+- **`ng update` can stop with `The Angular CLI requires a minimum Node.js version of ...`.** This happens when the first `@angular/` package in the command has no version number: `ng update` then runs with the newest Angular CLI, which requires a newer Node.js than Angular 21 does. Either update Node.js, or give that package a version number, as the command above does (`ng update @angular/fire@21.0.0-rc.1` for the release candidate, `ng update @angular/fire@21` once 21.0.0 is published).