fix: use standard ASP.NET Core 10 Blazor WASM runtime filename

Root cause analysis:
- App.razor referenced blazor.web.js (legacy filename)
- ASP.NET Core 10 publish outputs blazor.webassembly.js (standard)
- Build/publish mismatch caused 'SyntaxError: Invalid or unexpected token'

Solution (proper fix, not workaround):
- App.razor: change script src to blazor.webassembly.js
- Remove deploy_gb.sh file-copy workaround
- Program.cs: remove unnecessary comment

Result: Single source of truth - blazor.webassembly.js is the standard ASP.NET Core 10
filename. No file duplication, no symlinks, no publish-time workarounds needed.

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

src/TaxBaik.Web/Program.cs

@@ -397,8 +397,6 @@ if (!app.Environment.IsDevelopment())
 app.MapControllers();
 app.MapHealthChecks("/healthz");
 app.MapRazorPages();
-
-// MapStaticAssets must come before MapRazorComponents to ensure _framework/* files are served
 app.MapStaticAssets();
 
 // AllowAnonymous: JWT 미들웨어가 Blazor 셸 요청을 401로 차단하지 않도록 한다.