fix: simplify CI/CD WASM publish - remove manual copy conflict

ISSUE:
CI/CD was manually copying WASM files to TaxBaik.Web/wwwroot, causing:
- Conflicting assets error (same _framework/dotnet.js from 2 sources)
- Different fingerprints causing build failure

ROOT CAUSE:
TaxBaik.Web.csproj already references TaxBaik.Web.Client as ProjectReference.
dotnet publish automatically includes referenced projects.

SOLUTION:
1. Remove TaxBaik.Web/wwwroot/_framework/* (manual copies)
2. Simplify CI/CD: only run 'dotnet publish TaxBaik.Web/'
3. Let MSBuild handle dependency resolution (TaxBaik.Web.Client auto-included)

BUILD FLOW:
TaxBaik.Web (publish)
  ↓ (includes ProjectReference)
TaxBaik.Web.Client (auto-build)
  ↓ (generates WASM)
_framework/blazor.webassembly.js + WASM assemblies
  ↓ (merged to output)
./publish/wwwroot/  (complete)

Result: Clean, conflict-free build with proper WASM integration.

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

.gitea/workflows/deploy.yml

@@ -30,16 +30,7 @@ jobs:
       - name: Test solution
         run: dotnet test TaxBaik.sln -c Release --no-build
 
-      - name: Build WebAssembly client (WASM runtime generation)
-        run: dotnet publish TaxBaik.Web.Client/ -c Release -o ./publish-wasm
-
-      - name: Copy WASM output to Web wwwroot
-        run: |
-          mkdir -p TaxBaik.Web/wwwroot/_framework
-          cp -r ./publish-wasm/wwwroot/_framework/* TaxBaik.Web/wwwroot/_framework/
-          cp -r ./publish-wasm/wwwroot/index.html TaxBaik.Web/wwwroot/ 2>/dev/null || true
-
-      - name: Publish Web with WASM client
+      - name: Publish Web (auto-includes WASM from referenced TaxBaik.Web.Client)
         run: dotnet publish TaxBaik.Web/ -c Release -o ./publish --no-restore
 
       - name: Publish Proxy