Fix package-lock.json for tailwindcss upgrade

[continue]

This PR fixes the CI failure in #9112 by updating the package-lock.json files to be in sync with the package.json changes.

The Snyk PR updated tailwindcss to 3.4.18 but didn't update the lock files, causing npm ci to fail.

This PR:

• Updates extensions/vscode/package-lock.json to match tailwindcss@3.4.18
• Updates root package-lock.json with dependency changes

---

This agent session was co-authored by nate and Continue.

---

Summary by cubic

Sync package-lock.json files with the Tailwind CSS upgrade so npm ci succeeds again. This fixes the CI failure caused by mismatched lockfiles after the Snyk update.

• Bug Fixes
  • Updated extensions/vscode/package-lock.json to align with tailwindcss 3.4.x and refreshed related deps (jiti, lilconfig, postcss, chokidar).
  • Cleaned up root package-lock.json metadata to match current dependencies.
  • npm ci now passes in CI.

^{Written for commit 934cc36. Summary will update automatically on new commits.}

[continue]

Summary

This PR fixes the CI build failure in #9112 by synchronizing the package-lock.json files with the package.json changes.

The Problem

The Snyk PR updated tailwindcss from ^3.3.2 to ^3.4.18 in package.json, but the package-lock.json files weren't updated. When CI ran npm ci, it failed with:

Invalid: lock file's tailwindcss@3.4.14 does not satisfy tailwindcss@3.4.19

The Fix

Ran npm install --package-lock-only in the extensions/vscode directory to update:

• extensions/vscode/package-lock.json - Updated tailwindcss to 3.4.19 and related dependencies (jiti, lilconfig)
• Root package-lock.json - Updated peer dependency flags

Verification

The lock file now correctly shows tailwindcss@3.4.19, which satisfies the ^3.4.18 requirement in package.json. Once merged into the Snyk PR, the CI build should pass.

[cubic-dev-ai]

No issues found across 2 files