docs: note the removed @angular/platform-server peer in the v21 upgrade guide (#3795)

* docs: note the removed @angular/platform-server peer in the v21 upgrade guide

The upgrade guide's "Other notes" already lists the removed
@angular/platform-browser-dynamic peer. The optional
@angular/platform-server peer is gone too, and apps need no change.

* docs: name the removed peers once in the v21 upgrade guide

The line said "peer dependency" twice. Naming both packages before one "peer dependencies" reads better.

* docs: name 21.0.0-rc.2 in the upgrade guide's ng update example

The example named 21.0.0-rc.1, which would install the older release
candidate once 21.0.0-rc.2 is out.

* docs: note the App Check server-rendering change in the v21 upgrade guide

21.0.0-rc.2 skips App Check during server rendering (#3773). The guide
now says so and links the App Check page's server-rendering section.

Author: armando-navarro

docs/version-21-upgrade.md

@@ -81,5 +81,6 @@ Two symbols were removed rather than renamed. The migration leaves their imports
 ## Other notes
 
 - **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).
+- The obsolete `@angular/platform-browser-dynamic` and the unused optional `@angular/platform-server` peer dependencies were removed. No action is needed.
+- **App Check no longer runs during server rendering** (21.0.0-rc.2 and later). `inject(AppCheck)` returns `null` on the server. To keep it running there, provide `APP_CHECK_ON_SERVER` as `true` in your server config. See [App Check during server rendering](./app-check.md#server-side-rendering).
+- **`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.2` for the release candidate, `ng update @angular/fire@21` once 21.0.0 is published).