Prioritize panel config over route for add-on slug

When determining which add-on to load, check the panel config first
before falling back to the route path. This allows dedicated add-on
panels to always use their configured add-on regardless of the URL path.

Author: claude

src/panels/app/ha-panel-app.ts

@@ -113,15 +113,18 @@ class HaPanelApp extends LitElement {
     route?: Route,
     panel?: PanelInfo<AppPanelConfig>
   ): string | undefined {
-    // First check route path (e.g., /app/core_configurator)
+    // First check panel config (for dedicated add-on panels)
+    if (panel?.config?.addon) {
+      return panel.config.addon;
+    }
+    // Fall back to route path (e.g., /app/core_configurator)
     if (route?.path) {
       const slug = route.path.substring(1);
       if (slug) {
         return slug;
       }
     }
-    // Fall back to panel config
-    return panel?.config?.addon;
+    return undefined;
   }
 
   private async _fetchData(addonSlug: string) {