feat(demos): implement structured logging and cleanup debug statements

Replace console.log debugging with proper structured logging using Winston:

- Add winston logger with configurable LOG_LEVEL environment variable
- Replace all console.log/error statements with structured logging
- Remove verbose debug logging from API routes
- Keep valuable operational logging (errors, tenant operations, user events)
- Add log level configuration to environment documentation

Logging levels available:
- error: Critical issues only
- warn: Warnings and errors
- info: General information (default)
- debug: Detailed debugging information

This provides better observability while reducing noise in production.

Author: leggetter

examples/demos/dashboard-integration/.env.example

@@ -8,4 +8,8 @@ NEXTAUTH_SECRET=your-secret-here-replace-with-long-random-string
 
 # ============================== Outpost Integration ==============================
 OUTPOST_BASE_URL=http://localhost:3333
-OUTPOST_API_KEY=demo-api-key-change-in-production
+OUTPOST_API_KEY=demo-api-key-change-in-production
+
+# ============================== Logging ==============================
+# Options: error, warn, info, debug
+LOG_LEVEL=info

examples/demos/dashboard-integration/README.md

@@ -101,6 +101,7 @@ This demo represents a common integration scenario where:
 | `NEXTAUTH_SECRET` | Auth.js secret key | `your-secret-here` |
 | `OUTPOST_BASE_URL` | Outpost base URL | `http://localhost:3333` |
 | `OUTPOST_API_KEY` | Outpost API key | `demo-api-key-change-in-production` |
+| `LOG_LEVEL` | Application logging level (`error`, `warn`, `info`, `debug`) | `info` |
 
 ### Outpost Configuration (.env.outpost)