Add Sentry source maps and release tracking

- @sentry/vite-plugin uploads source maps during Docker build
- Release tagged with git SHA (SENTRY_RELEASE) on both client and server
- Environment set to production/development for filtering
- CD passes SENTRY_AUTH_TOKEN + SENTRY_RELEASE as Docker build args
- docker-compose passes SENTRY_RELEASE to runtime containers

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

apps/planner/vite.config.ts

@@ -1,11 +1,25 @@
 import { reactRouter } from "@react-router/dev/vite";
+import { sentryVitePlugin } from "@sentry/vite-plugin";
 import tailwindcss from "@tailwindcss/vite";
 import { defineConfig } from "vite";
 import path from "node:path";
 import { yjsDevPlugin } from "./app/lib/vite-yjs-plugin.ts";
 
 export default defineConfig({
-  plugins: [tailwindcss(), reactRouter(), yjsDevPlugin()],
+  build: {
+    sourcemap: true,
+  },
+  plugins: [
+    tailwindcss(),
+    reactRouter(),
+    yjsDevPlugin(),
+    sentryVitePlugin({
+      org: "trails-qq",
+      project: "planner",
+      release: { name: process.env.SENTRY_RELEASE },
+      disable: !process.env.SENTRY_AUTH_TOKEN,
+    }),
+  ],
   resolve: {
     alias: {
       "~": path.resolve(__dirname, "./app"),