chore: update circuit dependencies

[partyplatter08-lab]

Summary

• Updated the tscircuit/circuit-json dependency stack to current registry releases, including @tscircuit/runframe, circuit-json, tscircuit, and related viewers/exporters.
• Added @tscircuit/runframe as a direct dependency because the app imports it directly, and added @tscircuit/props to align the latest tscircuit peer graph for production builds.
• Removed the tracked bun.lock, ignored Bun lockfiles, and kept bunfig.toml configured with [install.lockfile] save = false.
• Migrated biome.json to the Biome 2 schema required by the updated @biomejs/biome.

Validation

• npm exec --yes bun -- install passes from a clean node_modules state and does not emit bun.lock or bun.lockb. Bun prints peer warnings for the latest React/TypeScript/Three/circuit-json ecosystem ranges, but install exits 0.
• npm exec --yes bun -- run format passes.
• npm exec --yes bun -- run build passes.
• npm run build passes.
• npm outdated --json returns {} for direct dependencies.
• vite preview smoke test served the built / page and the built JS asset with HTTP 200 locally.

No live Vercel deployment was triggered from this environment. The local production build and static preview artifact were verified; the GitHub/Vercel preview deployment should be checked after PR creation.

/claim #79

[vercel]

@partyplatter08-lab is attempting to deploy a commit to the tscircuit Team on Vercel.

A member of the Team first needs to authorize it.