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/router/index.ts

@@ -337,6 +337,22 @@ router.beforeEach(async (to, _from, next) => {
   });
 
   try {
+    // Log boot-time configuration on first navigation
+    if (!_from) {
+      logger.info(
+        "[Router] 🚀 First navigation detected - logging boot-time 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,
+          targetRoute: to.path,
+          timestamp: new Date().toISOString(),
+        },
+      );
+    }
+
     // Skip identity check for routes that handle identity creation manually
     const skipIdentityRoutes = [
       "/start",