fix(settings): resolve server switching not applying immediately

- Fix database query logic in PlatformServiceMixin.$getSettings() to properly
  distinguish between master settings (ID) and account settings (DID)
- Add comprehensive logging for settings debugging with request IDs and
  component tracking
- Fix ProfileService initialization order in AccountViewView to use correct
  partnerApiServer after settings load
- Add URL flow testing interface in TestView for debugging server switching
- Enhance settings consistency validation and error handling

Resolves issue where profile server changes were saved but not applied due to
incorrect database query logic and settings priority handling.

Files changed: PlatformServiceMixin.ts, AccountViewView.vue, TestView.vue,
TopMessage.vue, main.ts, router/index.ts

Testing: Added comprehensive URL flow testing interface for validation

src/main.ts

@@ -13,6 +13,15 @@ const platform = process.env.VITE_PLATFORM || "web";
 
 logger.info(`[Main] 🚀 Loading TimeSafari for platform: ${platform}`);
 
+// Log all relevant environment variables for boot-time debugging
+logger.info("[Main] 🌍 Boot-time environment configuration:", {
+  platform: process.env.VITE_PLATFORM,
+  defaultEndorserApiServer: process.env.VITE_DEFAULT_ENDORSER_API_SERVER,
+  defaultPartnerApiServer: process.env.VITE_DEFAULT_PARTNER_API_SERVER,
+  nodeEnv: process.env.NODE_ENV,
+  timestamp: new Date().toISOString(),
+});
+
 // Dynamically import the appropriate main entry point
 if (platform === "capacitor") {
   logger.info(`[Main] 📱 Loading Capacitor-specific entry point`);