feat: Add centralized logging system with @link-stack/logger package

- Create new @link-stack/logger package wrapping Pino for structured logging
- Replace all console.log/error/warn statements across the monorepo
- Configure environment-aware logging (pretty-print in dev, JSON in prod)
- Add automatic redaction of sensitive fields (passwords, tokens, etc.)
- Remove dead commented-out logger file from bridge-worker
- Follow Pino's standard argument order (context object first, message second)
- Support log levels via LOG_LEVEL environment variable
- Export TypeScript types for better IDE support

This provides consistent, structured logging across all applications
and packages, making debugging easier and production logs more parseable.

apps/link/app/_actions/overviews.ts

@@ -3,6 +3,9 @@
 import { executeGraphQL, executeREST } from "app/_lib/zammad";
 import { getTicketOverviewCountsQuery } from "app/_graphql/getTicketOverviewCountsQuery";
 import { getTicketsByOverviewQuery } from "app/_graphql/getTicketsByOverviewQuery";
+import { createLogger } from "@link-stack/logger";
+
+const logger = createLogger('link-overviews');
 
 const overviewLookup = {
   Assigned: "My Assigned Tickets",
@@ -36,7 +39,7 @@ export const getOverviewTicketCountsAction = async () => {
 
     return counts;
   } catch (e) {
-    console.error(e.message);
+    logger.error({ error: e }, "Error occurred");
     return {};
   }
 };
@@ -91,7 +94,7 @@ export const getOverviewTicketsAction = async (name: string) => {
 
     return { tickets: sortedTickets };
   } catch (e) {
-    console.error(e.message);
+    logger.error({ error: e }, "Error occurred");
     return { tickets, message: e.message ?? "" };
   }
 };