Throw an error if cookie max length is exceeded

### Link to the code that reproduces this issue https://github.com/tomaspiaggio/big-cookie-nextjs-repro ### To Reproduce 1. Clone this repository 2. Make a GET request to the `/set-cookie` route. It'll set a large cookie (5000 characters). 3. Observe that the middleware logs "Cookie not found" instead of reading the cookie. ### Current vs. Expected behavior When a cookie larger than the standard 4KB limit is set via a route handler on Next, the cookie does not appear in the middleware's `request.cookies` object. This silent failure can lead to unexpected behavior in applications that rely on middleware to process cookies. **Expected behavior**: The application should throw an exception when attempting to set a cookie that exceeds size limits, making the issue immediately apparent during development or testing. **Actual behavior**: The cookie is silently not set, and middleware cannot access it without any error or warning. ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 24.0.0: Mon Aug 12 20:52:12 PDT 2024; root:xnu-11215.1.10~2/RELEASE_ARM64_T6020 Available memory (MB): 16384 Available CPU cores: 12 Binaries: Node: 22.11.0 npm: 10.9.0 Yarn: N/A pnpm: 10.13.1 Relevant Packages: next: 15.5.6 // Latest available version is detected (15.5.6). eslint-config-next: N/A react: 19.1.0 react-dom: 19.1.0 typescript: 5.9.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Cookies ### Which stage(s) are affected? (Select all that apply) next dev (local), Vercel (Deployed) ### Additional context <img width="217" height="231" alt="Image" src="https://github.com/user-attachments/assets/1611bb95-9a97-46d7-b358-ecf1e87a1315" /> We spent 7 hours debugging with the WorkOS team helping us remotely until we figured this out. We found this because we're building a marketplace integration usnig the WorkOS Vercel OAuth integration (which is the one t…