Fix over-caching with Dynamic IO caching in Next.js 15

Since its introduction in version 13, Next.js's aggressive default caching has caused issues with stale data and inconsistent behavior, particularly affecting developers using the App Router. In response, Next.js 15 introduces Dynamic IO caching, a feature that offers a more flexible and granular approach to managing what gets cached and when, thereby balancing performance and data freshness. This new model allows developers to opt out of caching by default, granting them fine-grained control over data handling without needing to constantly bypass default settings. Dynamic IO can be enabled experimentally, offering tools like `use cache`, `cacheTag()`, and `cacheLife()` to allow for a more deliberate caching strategy, which can be tailored to suit different components' needs within applications. This approach is designed to mitigate over-caching issues while maintaining performance, making it particularly beneficial for complex applications that require a mix of dynamic and static content. As these features continue to evolve, mastering them can provide a performance advantage and a more predictable approach to managing dynamic content in data-intensive applications.