deps: bump biome and turbo (patch/minor)

[Aymericr]

What does this PR do?

Patch/minor tooling bumps in the root package.json, with bun.lock regenerated by bun 1.4.2:

• @biomejs/biome ^2.4.16 → ^2.5.15
• turbo ^2.9.17 → ^2.11.8

Changes needed for Biome 2.5, each in its own commit:

• style: apply Biome 2.5 formatter output: the formatter now wraps long test.each([...])('name', fn) and similar curried calls differently. This touches 86 files and is formatter output only.
• test: use non-null assertions where Biome 2.5 flags unsafe optional chaining: correctness/noUnsafeOptionalChaining now catches (a?.b as T).c. All 24 hits are in test files, and they now use a!.b, which the surrounding tests already do (for example commits[0]!). Behavior doesn't change: the old code would have thrown a TypeError on undefined anyway.

Left out on purpose:

• lightningcss-* platform pins stay at 1.32.0. @tailwindcss/node@4.3.0 depends on lightningcss at exactly 1.32.0, and that is what bun.lock resolves. Moving the optional platform pins to 1.33.0 would make them disagree with the resolved lightningcss. They should move together with the Tailwind bump in [Deps] chore(deps): refresh MCP, rendering, framework and CSS dependencies #1037 (or after it), whenever Tailwind resolves 1.33.
• No changes to packages owned by [Deps] chore(deps): refresh MCP, rendering, framework and CSS dependencies #1037 or [Deps] upgrade @types/three to 0.186 to match three r186 #1061, and no changes to the TypeScript pins.

How to test

1. bun install --frozen-lockfile
2. bun run ci: check, skills:validate, check-types, test and build should all pass.

Locally, check (same 164 warnings / 9 infos as main, 0 errors), skills:validate, check-types and build pass. In this VM, bun run test hits a single ordering-dependent failure in packages/viewer/src/components/viewer/perf-monitor.test.tsx. It reproduces on unmodified main too and passes when the file runs alone; main's CI is green.

Screenshots / screen recording

N/A — non-visual change

Checklist

• I've tested this locally with bun dev
• My code follows the existing code style (run bun check to verify)
• I've updated relevant documentation (if applicable)
• This PR targets the main branch

  

---

Note

Low Risk
Tooling and test-only formatting/lint fixes; no production logic changes.

^{Reviewed by Cursor Bugbot for commit 6908fe4. Bugbot is set up for automated code reviews on this repo. Configure here.}