Implement developer mode for testing and analytics visibility

[cmaneu]

Feature Overview:
Implement a "dev mode" in the IQ Challenge game to help developers test both gameplay and telemetry. This mode features a visible debug panel inside the game, inspired by the design shown below:

Core Capabilities:

• Keystroke to launch developer mode
• When launched, add a property debug"=true to all telemetry event sends.
• Display all analytics and telemetry events live in a dedicated "Analytics Output" panel (see mock-up).
• Include a "Test Actions" section with buttons to simulate common gameplay scenarios, such as:
  • Answer correctly
  • Skip question
  • Earn time bonus
  • Add life
• Clearly indicate that the session is running in Dev/Debug mode (e.g., banner, colored border).

Benefits:

• Streamlines game and telemetry testing for developers.
• Provides immediate visibility into emitted analytics, including event names, types (gameplay, session, identity), payload, timestamps, user/session context.
• Ensures all telemetry is sent for various states: start, question, bonuses, lives, level transitions, and edge cases.

Implementation Notes & Suggestions:

• Dev mode toggle: enable/disable via config, URL flag, or keyboard shortcut.
• Debug panel layout:
  • Bottom-of-screen overlay, styled as dark "terminal" section that doesn't block normal gameplay UI.
  • Test Actions: buttons for all crucial flows (as seen in the mock-up), including error simulation/resetting state.
  • Analytics Output: auto-streams events in real time, shows event name, type, key payload fields, timestamp, and identifiers. Option to filter or pause output.
  • Optionally: allow copying event payloads, support expanding/collapsing JSON output for easier inspection.
• Reference all relevant game and telemetry hooks, including session, question, timer, and scoring events.

---

This feature accelerates development, debugging, and telemetry validation for contributors working on analytics, gameplay instrumentation, or QA workflows.