Debug/sentry initialization

[KyleTryon]

This pull request adds comprehensive Sentry debug logging and diagnostics across both backend (cloudflare.ts, hono/app.ts) and frontend (main.tsx) code, making it easier to verify Sentry configuration, initialization, and runtime status in all environments. Logging is now always enabled (not just in development), and diagnostic endpoints and test messages are included to confirm Sentry is working as expected.

Sentry Debug Logging and Diagnostics

Backend (cloudflare.ts, hono/app.ts):

• Added detailed debug logs to Sentry initialization and configuration in cloudflare.ts, including checks for DSN existence, length, and available environment keys. Logging now uses console.error for missing DSN and is always enabled. [1] [2]
• Enhanced HTTP middleware in hono/app.ts to log Sentry status and span creation for every request, with warnings if Sentry is not configured.
• Improved /debug-sentry endpoint to provide comprehensive diagnostics, including runtime info, DSN details, available Sentry methods, environment keys, and attempts to send test errors and logs to Sentry, with robust error handling.

Frontend (main.tsx):

• Added always-on debug logs for Sentry DSN status, type, length, and all VITE env keys before initialization. Sentry configuration is logged in detail regardless of environment.
• Sentry initialization and test message sending are now logged in all environments, not just development. Errors in initialization or test message sending are logged as well.

[KyleTryon]

@sentry review