feat: telemetry engine integration and CI build optimization

[Yashh56]

Overview

This PR introduces a complete telemetry and analytics engine using Aptabase, deeply integrated across both the Rust backend and React frontend. It features a robust, privacy-first implementation allowing users to opt out of tracking.

Additionally, it resolves critical CI build failures on Windows by standardizing the pnpm workflow and securely embedding build-time environment variables.

Key Changes

📊 Analytics & Privacy

• Aptabase Integration: Configured @aptabase/tauri in the Rust backend (main.rs) and initialized tracking for app lifecycle events.
• Privacy Controls: Implemented a new settings toggle (AnalyticsSettings.tsx) allowing users to dynamically opt in or out of analytics.
• Frontend Wrapper (analytics.ts): All telemetry events (Git actions, AI queries, migrations, chart creation) now flow through a centralized wrapper that strictly respects the user's IPC-fetched privacy settings before dispatching.

🛠️ CI & Build Optimizations

• Secure Key Injection: Switched from runtime std::env::var to compile-time option_env!("APTABASE_APP_KEY") in main.rs to securely embed the analytics key into the release binary.
• Windows Packaging Fix: Resolved the .exe missing errors on GitHub Actions. Standardized the build pipeline across package.json, package-bridge.mjs, and bridge/package.json to strictly use pnpm, preventing npm run/npx bin resolution conflicts.
• Workflow Updates: Added APTABASE_APP_KEY secrets injection to .github/workflows/release.yml.

Testing

• Verified aptabase events fire successfully on local debug builds when the privacy toggle is enabled.
• Verified no events fire when tracking is disabled in Settings.
• Validated tauri-action successfully completes the NSIS Windows build without os error 32 or missing asset errors.