unstable_cache does not deserialize dates

### Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.5.0: Mon Apr 24 20:52:24 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6000 Binaries: Node: 18.12.1 npm: 9.6.4 Yarn: 1.22.19 pnpm: 7.13.1 Relevant packages: next: 13.4.7-canary.2 eslint-config-next: N/A react: 18.2.0 react-dom: 18.2.0 typescript: 4.9.5 ``` ### Which area(s) of Next.js are affected? (leave empty if unsure) App directory (appDir: true), Data fetching (gS(S)P, getInitialProps) ### Link to the code that reproduces this issue or a replay of the bug https://github.com/SSardorf/next_unstable_cache_date_deserialization ### To Reproduce 1. `npm i` 2. `npx prisma generate` 3. `npx prisma db push` 4. `npx prisma db seed` 5. `npm run dev` When you first run the project, you'll see that it loads correctly (cause first prisma invocation will result in non-cached data) When you refresh, the cached data will be shown, and it'll throw an error, as `post.createdAt` is no longer a Date, but a string: `<p>{post.createdAt.toISOString()}</p>` ### Describe the Bug When you first run the project, you'll see that it loads correctly (cause first prisma invocation will result in non-cached data) When you refresh, the cached data will be shown, and it'll throw an error, as `post.createdAt` is no longer a Date, but a string: `<p>{post.createdAt.toISOString()}</p>` ### Expected Behavior unstable_cache should correctly de-serialize Dates. ### Which browser are you using? (if relevant) _No response_ ### How are you deploying your application? (if relevant) _No response_