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/step-definitions/common-steps.ts

@@ -104,7 +104,7 @@ When('I go back', async function () {
 
 When('I refresh the page', async function () {
   console.log('🌍 About to refresh page from URL:', world.page.url());
-  await world.page.reload({ waitUntil: 'domcontentloaded' });
+  await world.page.reload({ waitUntil: 'networkidle' });
   console.log('🌍 Page refreshed, new URL:', world.page.url());
   // Wait extra time for full render
   await world.page.waitForTimeout(2000);