fix: change CI/CD publish to include WebAssembly client

Problem: CI/CD was publishing only TaxBaik.Web/, excluding WebAssembly client
build output. This caused blazor.web.js to be missing from deployed package.

Solution: Change publish from 'TaxBaik.Web/' to '.' (solution root) to include
all projects:
- TaxBaik.Web.Client (WebAssembly client with blazor.web.js)
- TaxBaik.Web (server with MapRazorComponents configuration)
- All dependencies

Result: WebAssembly runtime and all interactive components now deploy correctly.

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

.gitea/workflows/deploy.yml

@@ -30,8 +30,8 @@ jobs:
       - name: Test solution
         run: dotnet test TaxBaik.sln -c Release --no-build
 
-      - name: Publish Web
-        run: dotnet publish TaxBaik.Web/ -c Release -o ./publish --no-restore
+      - name: Publish Web (with WebAssembly client)
+        run: dotnet publish . -c Release -o ./publish --no-restore
 
       - name: Publish Proxy
         run: dotnet publish TaxBaik.Proxy/ -c Release -o ./publish/proxy