fix: restore MapFallbackToFile-only WASM configuration (c960860 style)

Reverted to c960860's proven configuration:
- NO MapRazorComponents (pure static WASM delivery)
- MapFallbackToFile for admin/portal SPA routing
- UseStaticFiles("/admin") for path-based static file serving

Issue with blazor.boot.json:
- MapRazorComponents should auto-generate it, but doesn't in our setup
- c960860 also had no MapRazorComponents, suggesting static-only approach works
- SRI integrity check failures may be browser cache or other cause

Current approach (c960860):
- WASM files served as pure static assets ✅
- MapFallbackToFile routes SPA requests ✅
- Next: Direct browser testing to verify WASM renders

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

package.json

@@ -2,7 +2,6 @@
   "scripts": {
     "test:e2e": "playwright test",
     "test:e2e:headed": "playwright test --headed",
-    "test:e2e:smoke": "playwright test --grep @smoke",
     "test:e2e:public-smoke": "playwright test --project=\"Public Smoke\" tests/e2e/public-smoke.spec.ts",
     "test:e2e:admin-smoke": "playwright test --project=\"Admin Smoke\" tests/e2e/admin-smoke.spec.ts"
   },