bug: TypeScript 7 conflicts with Volar 2.4.30 peer dependencies #507

Describe the Bug

Volar 2.4.30 declares a typescript: <7 peer dependency, while OWS Editor currently uses TypeScript ^7.0.2 across the workspace.

This incompatibility was identified in Dependabot PR #506 and originates from Volar commit ddef86e, which explains that TypeScript 7 no longer ships the JavaScript API required by Volar 2.x.

Dependency installation and workspace typechecking currently succeed, but the declared compatibility mismatch remains.

• We should investigate downgrading TypeScript to ^6.0.0 across the entire workspace until Volar supports TypeScript 7.\

• Configure Dependabot to temporarily ignore TypeScript versions >=7.0.0

Steps to reproduce

1. Check pnpm-workspace.yaml, which declares typescript: ^7.0.2.
2. Inspect the peer dependencies of @volar/language-service@2.4.30 and @volar/monaco@2.4.30.
3. Observe that both require typescript: <7.

Expected Behavior

• The workspace uses a single TypeScript version compatible with Volar 2.x.
• Evaluate TypeScript ^6.0.0 as a temporary solution.
• Configure Dependabot to temporarily ignore TypeScript versions >=7.0.0, while continuing to receive updates within TypeScript 6.x.
• Dependency installation succeeds with strict peer dependency validation.
• Type checking, builds, and tests continue to pass without regressions.
• Multiple TypeScript versions in the workspace should be avoided.

Platform

Other — Development tooling / monorepo.

Additional Context

• OWS Editor Dependabot PR: chore(deps): bump the all-dependencies group across 1 directory with 13 updates #506
• Peer dependency conflict reported by Copilot: chore(deps): bump the all-dependencies group across 1 directory with 13 updates #506 (comment)
• Volar compatibility restriction: volarjs/volar.js@ddef86e