Option to opt out of revalidation when setting/deleting cookies in Server Actions

[brunorodmoreira]

Goals

1. A per-call way to set/delete a cookie in a Server Action without marking the path as revalidated (no server re-render of the page into the action response, no client router cache invalidation)
2. The cookie must still be delivered to the browser via Set-Cookie exactly as today
3. Default behavior unchanged, so revalidation stays opt-out, per mutation

Non-Goals

1. Not changing revalidation behavior in Route Handlers or Middleware (cookie mutations there never trigger it)
2. Not affecting revalidatePath/revalidateTag/refresh() — an opted-out cookie mutation must never cancel revalidation requested by those APIs
3. Not a global config. It should be per-call

Background

Today any cookies().set()/delete() in a Server Action forces a full page re-render server-side and invalidates client router caches, wasted work when the cookie doesn't affect rendered content (canonical case: refreshing a session cookie on every request). A prior work was already started by a maintainer in #84313 due to a report in https://x.com/madarco/status/1972314852036374833 approved by Guillermo but it's stale since September 2025.

Proposal

The same API from #84313: cookies().set(name, value, { revalidate: false }), object forms, and cookies().delete({ name, revalidate: false }). I already reworked in a brand new PR #98058, using MutableRequestCookiesAdapter instead.