fix: resolve schedule data staleness in production builds

- Replace window.location.reload() with router.refresh() in ScheduleGenerator, MatchEditor, RecalculateEloButton for proper Next.js cache invalidation
- Add revalidatePath() call after schedule generation in POST handler
- Add ownerId to tournament creation in cucumber tests for proper permission checks
- Assign tournament_admin role via Prisma after user creation in cucumber tests
- Fix TypeScript type annotations in hooks.ts (tournament id map)
- Update page reload to use networkidle in common-steps.ts
- Clear .next/ cache before cucumber tests in justfile
- Add .turbo to clean target
- Add comprehensive debug logging to schedule API route
- Document findings in docs/TROUBLESHOOTING_SCHEDULE_GENERATION.md

e2e/cucumber/support/hooks.ts

@@ -141,7 +141,7 @@ After(async function () {
         select: { id: true }
       });
       
-      const tournamentIds = testTournaments.map(t => t.id);
+      const tournamentIds = testTournaments.map((t: { id: number }) => t.id);
       
       if (tournamentIds.length > 0) {
         // Delete bracket matchups via Prisma

e2e/cucumber/support/world.ts

@@ -11,6 +11,7 @@ export interface WorldState {
   prisma: any; // Lazy-loaded PrismaClient
   baseURL: string;
   user?: {
+    id?: string;
     email: string;
     name: string;
     password: string;
@@ -32,6 +33,7 @@ export class World implements WorldState {
   prisma: any;
   baseURL: string;
   user?: {
+    id?: string;
     email: string;
     name: string;
     password: string;