Add Sentry integration

[Dmytro-Fedoryshyn]

In this changeset, we have integrated Sentry into MōStats to track basic app telemetry: production launches and unhandled JavaScript exceptions from the main and renderer processes.

Issue: #6

[Copilot]

Pull request overview

This PR integrates Sentry into MōStats to capture basic production launch and crash telemetry across both the main and renderer processes (Issue #6).

Changes:

• Add Sentry initialization in main (Node) and renderer (React) with build-time DSN injection and runtime gating.
• Extend renderer↔main IPC to provide application name/version for Sentry release.
• Wire SENTRY_DSN into the release GitHub Actions workflow and document the setup.

Reviewed changes

Copilot reviewed 10 out of 12 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
vite.config.ts	Adds build-time defines for Sentry config and adjusts main bundling/externalization.
src/renderer/sentry.ts	New renderer Sentry initializer using IPC metadata for the release string.
src/renderer/proto/app.proto	Adds ApplicationMetadata message and GetApplicationMetadata RPC.
src/renderer/main.tsx	Initializes Sentry before render and hooks React root error callbacks to Sentry.
src/main/sentry.ts	New main-process Sentry initializer, launch event, session capture, and fatal error flushing.
src/main/index.ts	Imports Sentry initializer early during main startup.
src/main/application.ts	Implements GetApplicationMetadata IPC handler.
README.md	Documents build-time DSN requirement and release secret usage.
package.json	Adds @sentry/node and @sentry/react dependencies.
package-lock.json	Locks new Sentry dependency graph.
.gitignore	Ignores local .env* files.
.github/workflows/release.yml	Exposes SENTRY_DSN secret to the release build job.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.