refactor: move umami and sentry to server side

components/analytics/AnalyticsProvider.tsx

@@ -8,19 +8,12 @@ import { getAppServices } from '@/lib/services/create-services';
  * AnalyticsProvider Component
  *
  * Automatically tracks pageviews on client-side route changes.
- * This component should be placed inside your layout to handle navigation events.
+ * This component handles navigation events for the Umami analytics service.
  *
- * @param {Object} props - Component props
- * @param {string} [props.websiteId] - The Umami website ID (passed from server config)
- *
- * @example
- * ```tsx
- * // In your layout.tsx
- * const { websiteId } = config.analytics.umami;
- * <AnalyticsProvider websiteId={websiteId} />
- * ```
+ * Note: Website ID is now centrally managed on the server side via a proxy,
+ * so it's no longer needed as a prop here.
  */
-export default function AnalyticsProvider({ websiteId }: { websiteId?: string }) {
+export default function AnalyticsProvider() {
   const pathname = usePathname();
   const searchParams = useSearchParams();
 
@@ -31,14 +24,12 @@ export default function AnalyticsProvider({ websiteId }: { websiteId?: string })
     const url = `${pathname}${searchParams?.size ? `?${searchParams.toString()}` : ''}`;
 
     // Track pageview with the full URL
+    // The service will relay this to our internal proxy which injects the Website ID
     services.analytics.trackPageview(url);
 
-    if (process.env.NODE_ENV === 'development') {
-      console.log('[Umami] Tracked pageview:', url);
-    }
+    // Services like logger are already sub-initialized in getAppServices()
+    // so we don't need to log here manually.
   }, [pathname, searchParams]);
 
-  if (!websiteId) return null;
-
   return null;
 }