feat: Add Application Insights exception tracking to rules API routes

[Copilot]

Rules API routes were only calling console.error on failure — no structured exception data (stack trace, message, request context) was flowing to Application Insights, making 500 errors from the related-rules fetch nearly impossible to diagnose.

Changes

New: lib/appInsights.server.ts

Thin server-side telemetry helper wrapping the applicationinsights Node.js SDK (already initialised in instrumentation.ts):

export function trackServerException(error: unknown, properties?: Record<string, string>): void
export function trackServerEvent(name: string, properties?: Record<string, string>): void

• Uses require() at call time (not import time) — safe across all server contexts
• No-ops silently when defaultClient is null (local dev, SDK not initialised)
• Inner try/catch ensures telemetry never crashes the caller

Updated API routes

trackServerException(err, { route: "..." }) added to all four rules error handlers:

Route	File
GET /api/rules	app/api/rules/route.ts
GET /api/rules/paginated	app/api/rules/paginated/route.ts
GET /api/tina/rule	app/api/tina/rule/route.ts
GET /api/tina/rules-by-author	app/api/tina/rules-by-author/route.ts

The route property surfaces in Application Insights as a custom dimension, allowing quick filtering in the Azure Portal.

Screenshot (optional)

N/A — server-side telemetry change; observable in Application Insights exceptions blade.

[Aibono1225]

/deploy

[joshbermanssw]

LGTM