docs: clarify serverless runtime behavior for use cache (#92232)
## Summary
- add a prominent note in the App Router Caching guide about runtime
behavior on serverless deployments
- clarify that `use cache` runtime entries are in-memory and may not
persist across requests when requests hit different instances
- link directly to `use cache: remote` as the durable/shared runtime
caching option
Closes #91959
## Verification
- **Manual/source verification**
- Confirmed before change there was no mention of serverless runtime
cache persistence in `docs/app/getting-started/caching`.
- Confirmed after change the new callout appears immediately under the
existing “Good to know” note in
`docs/01-app/01-getting-started/08-caching.mdx`.
- **Evidence screenshots (before/after + verification)**
- Before:
https://raw.githubusercontent.com/wwenrr/pr-evidence-images/main/next.js/issue-91959/2026-04-01/before.png
- After:
https://raw.githubusercontent.com/wwenrr/pr-evidence-images/main/next.js/issue-91959/2026-04-01/after.png
- Verification keyword check:
https://raw.githubusercontent.com/wwenrr/pr-evidence-images/main/next.js/issue-91959/2026-04-01/verification.png
## Notes
- Formatting toolchain was not run in this environment because `pnpm` is
unavailable on host (`pnpm: not found`).
- Change is a minimal docs-only edit (single file, two inserted lines in
a callout block).
---------
Co-authored-by: wwenrr <wwenrr@users.noreply.github.com>
Co-authored-by: Joseph Chamochumbi <joseph.chamochumbi@vercel.com>
Co-authored-by: Joseph <sephxd1234@gmail.com>