next.js

a3f4b3b1 - Link Cache Components config errors to the migration guide (#101348)

Link Cache Components config errors to the migration guide (#101348) ## Summary Link incompatible Cache Components route segment config errors directly to the existing migration guide, where the supported migration depends on each export's value and the route's rendering and caching requirements. Use the same migration-guide URL for the removed `experimental.dynamicIO` config diagnostic. This is a consistency improvement alongside the reported route-segment diagnostics gap. The change updates the shared compiler diagnostic and its affected development/e2e snapshots. Regression coverage checks both incompatible exports in one Route Handler and config loading with both `dynamicIO: true` and `dynamicIO: false`. Finding: https://next-maintainer-agent.vercel.tools/agent-feedback/4923 Related runtime documentation: #99820. ## Verification - `cargo test -p next-custom-transforms --test errors react_server_components_errors`: 38 passed with the migration-guide URL. - `pnpm exec jest --runInBand --runTestsByPath packages/next/src/server/config.test.ts`: 27 passed. Both new dynamicIO cases fail with the original URL and pass with the migration-guide URL. - Rust formatting, Prettier, ESLint, and `git diff --check` passed on the changed files. - The supplied dev/build variants were reproduced on `next@16.5.0-canary.43` before the change. The earlier diagnostic wording passed 29 focused integration tests across Turbopack/Webpack development and production and the affected Rspack development suite; those were not rerun after the final URL updates. - The full monorepo bootstrap remains blocked by missing worktree dependencies. The config suite exercises the updated TypeScript source directly. <!-- NEXT_JS_LLM -->