Update opennext and leverage "use cache" on CF

[SamyPesse]

No description provided.

[github-actions]

Summary of the deployments:

Version 1

Version	URL	Status
Latest commit	https://4f5518a0.gitbook-open.pages.dev	✅
PR	https://pr3204.gitbook-open.pages.dev	✅

Version 2

Version	URL	Status
Vercel	https://gitbook-v2-pbxbb4du6-gitbook.vercel.app	✅
Cloudflare	https://bdbd19d5-gitbook-open-v2-preview.gitbook.workers.dev	✅

Test content

Site	v1	2v	2c
GitBook	https://4f5518a0.gitbook-open.pages.dev/gitbook.com/docs	https://gitbook-v2-pbxbb4du6-gitbook.vercel.app/url/gitbook.com/docs	https://bdbd19d5-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs
E2E	https://4f5518a0.gitbook-open.pages.dev/gitbook.gitbook.io/test-gitbook-open	https://gitbook-v2-pbxbb4du6-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open	https://bdbd19d5-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.gitbook.io/test-gitbook-open

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
customers-v1 (Inspect)	✅ No changes detected	-	May 16, 2025, 12:48 PM
customers-v2 (Inspect)	👍 Changes approved	79 changed	May 16, 2025, 12:51 PM
default (Inspect)	👍 Changes approved	1 changed	May 16, 2025, 12:53 PM
v2-cloudflare (Inspect)	✅ No changes detected	-	May 16, 2025, 12:54 PM
v2-vercel (Inspect)	✅ No changes detected	-	May 16, 2025, 12:53 PM

[changeset-bot]

⚠️ No Changeset found

Latest commit: c9df34e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[conico974]

I think the only thing missing here would be to wait for this opennextjs/opennextjs-cloudflare#666 to be merged and released so that we could use npm release instead of pkg.pr.new

[SamyPesse]

I think we can merge and deploy it already to test with a bit of traffic

[conico974]

LGTM