fix: replace console.log/console.error with proper logging in monitoring and themes routes

- monitoring.js: Added log dependency, replaced console.log with log.warn
- themes.js: Added log dependency, replaced console.error with log.error
- src/app.js: Pass log to monitoringRoutes and themesRoutes

This fixes error messages being lost to stdout instead of proper log files.

dashcaddy-api/routes/monitoring.js

@@ -7,9 +7,10 @@ const { success } = require('../response-helpers');
  * @param {Object} deps.resourceMonitor - Resource monitoring manager
  * @param {Object} deps.docker - Docker client wrapper
  * @param {Function} deps.asyncHandler - Async route handler wrapper
+ * @param {Object} deps.log - Logger instance
  * @returns {express.Router}
  */
-module.exports = function({ resourceMonitor, docker, asyncHandler }) {
+module.exports = function({ resourceMonitor, docker, asyncHandler, log }) {
   const router = express.Router();
 
   // ===== RESOURCE MONITORING ENDPOINTS =====
@@ -119,7 +120,7 @@ module.exports = function({ resourceMonitor, docker, asyncHandler }) {
         });
       } catch (e) {
         // Skip containers we can't get stats for
-        console.log(`Could not get stats for ${containerInfo.Names[0]}:`, e.message);
+        log.warn('monitoring', `Could not get stats for ${containerInfo.Names[0]}`, { error: e.message });
       }
     }