chore: update dependencies and migrate to pnpm 11.5.2

[kimhongyeon]

Affected Package(s)

• @heripo/pdf-parser
• @heripo/document-processor
• @heripo/model
• @heripo/logger
• @heripo/shared (internal)
• demo-web
• docs
• Other (root configs, CI, etc.)

Summary

This PR refreshes workspace dependencies and migrates the monorepo from pnpm 10 to pnpm 11.5.2. It keeps package manager configuration compatible with pnpm 11 while updating root, catalog, demo-web, and pdf-parser dependency versions.

Changes

• Updated root package.json dev dependencies including @types/node, eslint, turbo, typescript-eslint, and vite.
• Updated pnpm-workspace.yaml catalog versions for AI SDK packages, Vitest packages, ai, ai-sdk-ollama, and es-toolkit.
• Updated apps/demo-web/package.json dependencies including Next.js, React, Radix UI, TanStack packages, Lucide, OTP, PostCSS, and related type packages.
• Updated packages/pdf-parser/package.json to use yauzl 3.3.2 and @types/yauzl ^3.3.0.
• Updated root packageManager from pnpm@10.33.2 to pnpm@11.5.2.
• Moved pnpm overrides from package.json into pnpm-workspace.yaml.
• Replaced ignoredBuiltDependencies with pnpm 11 allowBuilds entries for esbuild and sharp.
• Regenerated pnpm-lock.yaml with refreshed dependency resolutions under pnpm 11.5.2.
• Updated README and CONTRIBUTING references from pnpm 10 to pnpm 11.

Breaking Changes

• None
• If any, describe migration steps:

Checklist

• I followed the Code of Conduct (see CODE_OF_CONDUCT.md)
• I ran: pnpm lint pnpm typecheck pnpm build pnpm test
• Tests added/updated; coverage remains 100%
• Docs/README updated if needed
• No external side effects (network/file/process/time) in tests — use mocks

Related Issues

Closes #