fix(ci): resolve deployment failure with legacy-peer-deps

Issue:
- GitHub Pages deployment failing on dependency installation
- Eslint v9 incompatible with eslint-config-next peer dependency
- Peer dependency conflict blocking npm install

Fix:
- Add --legacy-peer-deps flag to pnpm install in CI workflow
- Allows installation despite peer dependency mismatches
- Matches local development environment setup

Impact:
- Website will auto-deploy on push to main
- v1.2.0 features will be available in playground
- No functional changes to site code

Testing:
- Local build successful with --legacy-peer-deps
- Next.js build completes without errors
- Site functions normally with v1.2.0 parser

Refs: Deployment failure in run #18587251683

Author: alpha912

.github/workflows/deploy.yml

@@ -33,7 +33,7 @@ jobs:
           cache: 'pnpm'
 
       - name: Install dependencies
-        run: pnpm install --frozen-lockfile
+        run: pnpm install --frozen-lockfile --legacy-peer-deps
 
       - name: Build site
         run: pnpm run build