Add backend build step and use --no-build

In the reusable load concurrency workflow, add an explicit dotnet build for backend/src/Taskdeck.Api/Taskdeck.Api.csproj (Release, no-restore) before starting the API. Also pass --no-build to dotnet run so the already-built artifacts are used and an implicit rebuild is avoided. This ensures the API is built ahead of the load harness, speeds up CI, and prevents potential rebuild-related race conditions.

Author: Chris0Jeky

.github/workflows/reusable-load-concurrency-harness.yml

@@ -77,6 +77,9 @@ jobs:
         working-directory: frontend/taskdeck-web
         run: npx playwright install --with-deps chromium
 
+      - name: Build backend
+        run: dotnet build backend/src/Taskdeck.Api/Taskdeck.Api.csproj --configuration Release --no-restore
+
       - name: Reset harness result folders
         run: |
           rm -f frontend/taskdeck-web/taskdeck.load.k6.ci.db
@@ -95,7 +98,7 @@ jobs:
         run: |
           set -euo pipefail
 
-          dotnet run --project backend/src/Taskdeck.Api/Taskdeck.Api.csproj --configuration Release --no-restore \
+          dotnet run --project backend/src/Taskdeck.Api/Taskdeck.Api.csproj --configuration Release --no-restore --no-build \
             > frontend/taskdeck-web/test-results/load/backend-load-api.log 2>&1 &
           api_pid=$!