Missing priority option.

[linkthai]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the bug has not already been reported

Fastify version

4.25.2

Plugin version

9.3.0

Node.js version

20.5.1

Operating system

macOS

Operating system version (i.e. 20.04, 11.3, 10)

Sonoma

Description

The priority options was removed in 9.2.0, and the cookies are defaulted to priority Medium now.

9e4652f

Steps to Reproduce

reply.cookie(
      AUTH_COOKIE,
      JSON.stringify({
        accessToken,
        refreshToken,
        metadata,
        refreshTokenExpiresAt,
      }),
      {
        maxAge: new Date(refreshTokenExpiresAt).getTime() / 1000,
        httpOnly: true,
        sameSite: 'none',
        priority: 'high', <--- causing type error
      },
    );```

### Expected Behavior

The priority options have typings and it works.

[gurgunday]

The type was there but I couldn’t find the real code, and assumed it didn’t exist, I’ll take another look

[gurgunday]

Seems like that option didn’t really exist for a while now

I don’t see Priority defined in RFC 6265 either

Do you really need it?

[linkthai]

Seems like that option didn’t really exist for a while now

Is it? In the 9.1.0, the cookie I created could use priority High and the cookie is actually on top of the cookie list. In the 9.3.0, the cookie is always Medium in the middle of the list.

I'm not sure if it 100% neccessary, but it's my authentication cookie. If I have an option to make its priority as high as I could I would do it.

I'm not acknowledged about RFC requirements, but Priority is an actual mechanism that is used by current browsers. And there is no mention or indication that they were deprecated, I can't find them anywhere (!). So I don't see why it was removed when it still being implemented by the browsers.

[climba03003]

The PR that removed the priority is #260 which we change from cookie to our own implementation.

We can change it back to using cookie as it support Partitioned now. or we should copy the same set of test to prevent regression on cookies handling.
@mcollina WDYT?

[gurgunday]

I vote on keeping the fork and adding it here

[mcollina]

I think we should keep the fork at this point. We have been adding it back every now and then because of the slow responsiveness of cookie and unless we see some change there, I expect we would need to fork again in the future.

[Uzlopak]

Created PR #275