fix: resolve admin interactivity by unifying to Server render mode

Problem: Mixed WebAssembly (App) and Server (Login) render modes caused interaction breakage after login. Panels, accordions, and menu selections failed because render mode changed during page navigation.

Solution: Unified all admin components to InteractiveServerRenderMode for consistent interactivity:
- App.razor: Routes and HeadOutlet use InteractiveServerRenderMode
- Login.razor: Already uses InteractiveServerRenderMode
- Program.cs: Removed WebAssembly component registration

Updated validation script to require Server mode instead of WebAssembly for admin shell.

This ensures:
✅ Consistent render mode throughout admin UI
✅ Reliable component interactivity (panels, accordions, menus)
✅ Stable page navigation and state management

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

TaxBaik.Web/Program.cs

@@ -71,11 +71,10 @@ builder.Services.AddRateLimiter(options =>
     });
 });
 
-// Razor Pages + Blazor Server/WebAssembly 통합
+// Razor Pages + Blazor Server 통합
 builder.Services.AddRazorPages();
 builder.Services.AddRazorComponents()
-    .AddInteractiveServerComponents()
-    .AddInteractiveWebAssemblyComponents();
+    .AddInteractiveServerComponents();
 builder.Services.Configure<Microsoft.AspNetCore.Components.Server.CircuitOptions>(options =>
 {
     options.DetailedErrors = true;
@@ -391,8 +390,6 @@ app.MapStaticAssets();
 // 인증은 Blazor AuthorizeRouteView → RedirectToLogin 에서 처리한다.
 app.MapRazorComponents<TaxBaik.Web.Components.Admin.App>()
    .AddInteractiveServerRenderMode()
-   .AddInteractiveWebAssemblyRenderMode()
-   .AddAdditionalAssemblies(typeof(TaxBaik.WasmClient._Imports).Assembly)
    .AllowAnonymous();
 
 // 애플리케이션 시작/종료 로깅