Improve Cache Components behavior in `next dev` for public `'use cache'` values with an explicitly short expiration, including `cacheLife({ expire: 0 })` and short built-in profiles.

On a cold request or client navigation, the cache function should still execute normally and a surrounding Suspense fallback should be observable while it streams. Once populated, the entry must remain usable across development reloads long enough for a warm navigation or reload to serve the previously cached value immediately, without showing the fallback or blocking on regeneration. This must work with both the built-in default cache and a configured custom cache handler.

Dynamic request renders that consume one of these short-expiration entries must also refresh it in the background. The current request should receive the stale cached value, while a later reload converges to the newly computed value. For custom handlers, refreshing must execute the cache function and write the result through to the configured backing handler.

Do not rewrite or broaden the value's resolved cache lifetime to achieve this. Its actual short `expire` must continue to control staging and cache-life propagation, so client-only values remain excluded from the static shell and nested caches are not incorrectly classified as dynamic. The change is development-only: production expiration and configured-handler behavior must remain unchanged.

Preserve the existing development cache optimizations for private caches and `cacheMaxMemorySize: 0`. Also preserve custom-handler coherence: if the backing cache is invalidated or purged out of band, a development fast-path must stop serving its stale copy and eventually regenerate rather than retaining it indefinitely.