Use Cache Components as the internal PPR signal (#96827)
## Summary
`experimental.ppr` is deprecated, and configuring it with a truthy value
already produces an error. However, enabling Cache Components still
backfilled this option internally, and several build and runtime paths
continued treating it as the source of truth for PPR.
This change:
- uses `cacheComponents` directly for application and route PPR checks
- removes the internal `experimental.ppr` backfill and associated
plumbing
- deletes the obsolete PPR configuration helpers
- removes legacy PPR telemetry and an unreachable non-Cache-Components
workaround
- preserves the deprecated config type, schema, and migration error for
user-provided `experimental.ppr`
This does not change supported behavior: Cache Components already
implied `experimental.ppr: true` internally, so these checks resolve to
the same value.
<!-- NEXT_JS_LLM -->
---------
Co-authored-by: Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>