Fix Ballpit TypeScript errors: migrate THREE.Clock to THREE.Timer

[Copilot]

Ballpit raised TypeScript errors and THREE.Clock deprecation warnings on modern three.js. Root cause: the package shipped three@^0.167.1 while already declaring @types/three@^0.180.0 — a mismatch where Clock is deprecated (removed in newer releases) and Timer lives in three's core.

Changes

• Align runtime with types: bump three ^0.167.1 → ^0.180.0 (@react-three/* peer ranges are >=0.156).
• Clock → Timer in all four Ballpit sources (ts-default, ts-tailwind, content jsx, tailwind jsx):
  • timer.update() before getDelta() each frame
  • clock.start() (resume) → timer.reset()
  • drop clock.stop() — pause/visibility already handled by the component
  • timer.dispose() on cleanup
• Regenerated public/r/*.json registry via npm run registry:build (Ballpit sources + three@^0.180.0 dependency strings).

Animation loop

// before
this.#animationState.delta = this.#clock.getDelta();
// after
this.#timer.update();
this.#animationState.delta = this.#timer.getDelta();

Notes

• Non-Ballpit registry diffs are auto-generated dependency-string bumps (three@^0.167.1 → ^0.180.0).
• Pre-existing, unrelated tsc errors remain in SideRays, Lanyard, and SplitText.