fix(keycloak): update user club attributes with real database UUIDs

- Replaced placeholder UUIDs (club-1-uuid, club-2-uuid) with real database UUIDs
- Updated all 5 test users via Keycloak database
- Restarted Keycloak to clear caches and apply changes

Impact:
- JWT tokens now contain real UUIDs in clubs claim
- API endpoints accept X-Tenant-Id with real UUIDs (returns 200 OK)
- Unblocks 46 remaining QA scenarios

Documentation:
- Created update-keycloak-club-uuids.py script for automation
- Added KEYCLOAK_UPDATE_GUIDE.md with step-by-step instructions
- Recorded learnings in notepad

Ref: .sisyphus/evidence/final-f3-manual-qa.md lines 465-512

.sisyphus/evidence/final-qa/qa-execution-log.md

@@ -0,0 +1,16 @@
+# F3: Real Manual QA — Execution Log
+
+## Environment Setup
+✅ PostgreSQL: HEALTHY (port 5432)
+✅ Keycloak: RUNNING (port 8080, realm: workclub)
+✅ Frontend: RUNNING (port 3000)
+✅ API: HEALTHY (port 5001, /health/live returns 200)
+✅ Test users: All passwords reset to testpass123
+✅ Token acquisition: Working (admin@test.com authenticated successfully)
+
+---
+
+## TASK 1: Git Repository Scaffold
+
+**QA Scenarios:**
+Timestamp: Do.  5 März 2026 11:25:47 CET