chore(deps): update dependency cookie to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
cookie	^1.1.1 → ^2.0.0

---

Release Notes

jshttp/cookie (cookie)

v2.0.1

Compare Source

Improved:

• Small performance improvement by incrementing = index while parsing set-cookie (#​280)

v2.0.0

Compare Source

Important: This release moves the package to ESM only. In node 22+ you can require(esm), and older node versions are not supported.

Changed

• Switch to ESM (#​273)
• Remove deprecated code paths (#​272)
  • The old parse and stringify methods have been renamed: parseCookie and stringifySetCookie
  • stringifySetCookie only supports object mode (e.g. { name: "", value: "" })

Improvements

• Faster stringify cookie (#​262)
• Optimize encode performance (#​269)
• Apply encode to empty cookie values (#​277)

Fixed

• Omit leading semicolon when stringifying cookies with skipped values (#​267)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (1170 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
.                                        | [WARN] deprecated conventional-changelog-cli@5.0.0
Progress: resolved 156, reused 0, downloaded 0, added 0
Progress: resolved 322, reused 0, downloaded 1, added 0
Progress: resolved 421, reused 0, downloaded 1, added 0
Progress: resolved 589, reused 0, downloaded 1, added 0
Progress: resolved 681, reused 0, downloaded 1, added 0
Progress: resolved 955, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (1170 entries in 6.8s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 5 lockfile entries failed verification:
  @intlify/core-base@11.4.7 was published at 2026-07-20T12:17:48.918Z, within the minimumReleaseAge cutoff (2026-07-20T05:30:31.669Z)
  @intlify/devtools-types@11.4.7 was published at 2026-07-20T12:17:53.129Z, within the minimumReleaseAge cutoff (2026-07-20T05:30:31.669Z)
  @intlify/message-compiler@11.4.7 was published at 2026-07-20T12:17:57.178Z, within the minimumReleaseAge cutoff (2026-07-20T05:30:31.669Z)
  @intlify/shared@11.4.7 was published at 2026-07-20T12:18:05.951Z, within the minimumReleaseAge cutoff (2026-07-20T05:30:31.669Z)
  vue-i18n@11.4.7 was published at 2026-07-20T12:18:10.681Z, within the minimumReleaseAge cutoff (2026-07-20T05:30:31.669Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.