fix: I address the 18 react-hooks lint warnings from the ESLint 9 upgrade

[zaccesss]

Closes #190

One (app/faq/page.tsx) was a genuine issue, a running index counter mutated during render, replaced with a precomputed per-section offset. The other 17 are legitimate, documented patterns that this new rule set cannot distinguish from unsafe code, each annotated with a scoped, justified eslint-disable rather than rewritten:

• 14 cases of syncing React state from an external source on mount or dependency change (localStorage, DOM classList, a fetch), which is the pattern react.dev itself documents for effects
• 1 intentional ref read in TelemetryChart.tsx that batches WebSocket pushes between polls rather than re-rendering on every message
• 2 warnings on the same recursive-reconnect closure in useWebSocketTelemetry.ts, a standard self-referencing setTimeout pattern that is safe because the closure only runs after the function's own declaration has completed

Removed the file-wide warn-level downgrade from eslint.config.mjs now that every flagged line has a precise justification instead.

[zaccesss]

Checked the faq/page.tsx rewrite against the original output (same numbering, now a pure computation), and spot-checked several of the eslint-disable justifications against the actual code, they hold up. Good to merge.