Bump Vercel CLI pin to 59.16.0 for pnpm 12

[yamcodes]

Description

Bump the pinned Vercel CLI from 54.7.1 → 59.16.0 in the three www deploy workflows on dev.

vercel@54.7.1 invokes pnpm with --unsafe-perm, which pnpm 12 removed. That broke preview deploys on dev after the pnpm 12 bump (failed run: https://github.com/yamcodes/arkenv/actions/runs/34621903135).

Companion to #1832 (same pin bump on v1). CI-only; no changeset.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor

Checklist

• My code follows the code style of this project (double quotes, tabs, no parameter reassignment).
• I have written sentence-case imperative commits / PR title (e.g. Add support for custom error messages - no feat:, no trailing period, capitalized).
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have created a changeset using pnpm changeset (if this affects a published package).

For v0 (dev) PRs:

• Forward-Porting: Already landed on v1 via fix(ci): use Vercel CLI compatible with pnpm 12 #1832; this is the dev follow-up.

  

[changeset-bot]

⚠️ No Changeset found

Latest commit: a615713

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