chore: pin packageManager to pnpm@10.33.4 to match the vite consumer

The vite PR's pnpm is 10.33.4. When it consumes vite-task as a git dep,
declaring pnpm@11.1.2 here forces a version switch during the
prepare/pack flow, which produces an install that vite's outer pnpm 10
can't resolve (TS2307 "Cannot find module @voidzero-dev/vite-task-client"
at typecheck time even though pnpm install reports success).

Aligning the versions fixes the integration. We can revert once
@voidzero-dev/vite-task-client is published to npm and the github:
spec is no longer needed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: wan9chi

package.json

@@ -25,5 +25,5 @@
   "engines": {
     "node": "^20.19.0 || >=22.12.0"
   },
-  "packageManager": "pnpm@11.1.2"
+  "packageManager": "pnpm@10.33.4"
 }