Feat cache for the queue

[conico974]

Durable object queue should already be able to handle most situation, but there is a case where for a single route, while being stale, you reach the limits of what a single durable object is capable of handling.

For this kind of cases, adding cache in front will help (but in case of error between the worker and the durable object, revalidation may take more time to happen)

There is 1 other upgrade that we could do for this case:

• Create a proxy durable object in front of the durable queue, it would have some logic to deduplicate in memory and to handle backpressure for the other durable object.

[changeset-bot]

🦋 Changeset detected

Latest commit: 56dca94

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@opennextjs/cloudflare	Minor

Not sure what this means? Click here to learn what changesets are.

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

[pkg-pr-new]

Open in StackBlitz

pnpm add https://pkg.pr.new/@opennextjs/cloudflare@496

commit: 56dca94

[vicb]

Let's merge this for 1.1.

Could you please work on a doc PR when you have time to describe the Queue Cache and the options so that we can merge at the same time.

[vicb]

Doc in opennextjs/docs#156

[vicb]

LGTM

Let's add this to the next minor