fix: route all console.error through ErrorHandler for consistent tracking

Converted 35+ raw console.error calls to use ErrorHandler.logError() across
12 files. ErrorHandler provides structured logging, local error storage,
and error tracking integration.

Files:
- app-selector.js: 4 errors (fetch templates, port check, suggested port, deploy)
- globals.js: 2 errors (CSRF token get/add)
- service-credentials.js: 2 errors (save/clear credentials)
- totp-settings.js: 4 errors (TOTP setup, session duration, disable, AuthCard)
- notification-settings.js: 2 errors (load config, load history)
- setup-wizard.js: 2 errors (save config to server)
- progress-tracker.js: 4 errors (storage read/write/session/fallback)
- tooltip-definitions.js: 2 errors (validation, condition eval)
- tour-manager.js: 2 errors (Driver.js not loaded, tooltip not found)
- theme-adapter.js: 1 error (theme change callback)
- weather.js: 1 error (weather update)
- onboarding.js: removed duplicate console.error, fixed 2 remaining calls

All console.error calls in the DashCaddy frontend now go through ErrorHandler.

status/js/theme-adapter.js

@@ -7,6 +7,8 @@
 (function(window) {
   'use strict';
 
+  const errorHandler = new ErrorHandler();
+
   const debug = (...args) => {
     if (window.DASHCADDY_DEBUG) { console.log(...args); }
   };
@@ -190,7 +192,7 @@
         try {
           callback(newTheme, oldTheme);
         } catch (error) {
-          console.error('[ThemeAdapter] Error in theme change callback:', error);
+          errorHandler.logError('[ThemeAdapter] Theme Change Callback', error, { function: '_notifyThemeChange' });
         }
       });
     }