feat: Implement tournament schedule tab and fix E2E tests (#27)

## Summary

This PR implements the tournament schedule tab functionality and fixes all remaining E2E test failures.

### Changes Included

1. **Tournament Schedule Feature**
   - Added tournament schedule page at `/admin/tournaments/[id]/schedule`
   - Implemented "Generate Schedule" button functionality
   - Added schedule generation logic for round-robin tournaments

2. **E2E Test Fixes**
   - Fixed database connection issues in production builds
   - Improved test reliability with better error handling and debugging
   - Updated test infrastructure to use environment variables instead of hardcoded values

3. **CI/CD Updates**
   - Added E2E test job to PR workflow
   - Configured tests to run against development database
   - Moved database password to Gitea secrets

4. **Code Quality**
   - Removed hardcoded passwords from codebase
   - Improved Prisma client configuration
   - Enhanced authentication and navigation components

### Test Results
All 16 E2E test scenarios are now passing:
- Authentication tests: ✅
- Registration tests: ✅
- Tournament schedule tests: ✅
- Player schedule tests: ✅
- Admin navigation tests: ✅

### Database Configuration
- Tests run against `euchre_camp_dev` database
- Production builds use environment variables for database configuration
- Database password stored in Gitea secrets as `DB_PASSWORD`

### CI Pipeline
The PR workflow now includes:
1. Unit tests
2. E2E tests (using production build)
3. Version bump analysis

E2E tests must pass before PR can be merged.

Reviewed-on: #27
Co-authored-by: David Gwilliam <dhgwilliam@gmail.com>
Co-committed-by: David Gwilliam <dhgwilliam@gmail.com>

src/app/admin/matches/page.tsx

@@ -15,10 +15,10 @@ interface Match {
     id: number
     name: string
   } | null
-  team1P1: { id: number; name: string }
-  team1P2: { id: number; name: string }
-  team2P1: { id: number; name: string }
-  team2P2: { id: number; name: string }
+  player1P1: { id: number; name: string }
+  player1P2: { id: number; name: string }
+  player2P1: { id: number; name: string }
+  player2P2: { id: number; name: string }
 }
 
 export default function AdminMatchesPage() {
@@ -58,6 +58,16 @@ export default function AdminMatchesPage() {
         method: "DELETE",
       })
 
+      if (!response.ok) {
+        try {
+          const errorData = await response.json()
+          alert(`Error: ${errorData.error || 'Failed to delete match'}`)
+        } catch {
+          alert(`Error: ${response.status} ${response.statusText}`)
+        }
+        return
+      }
+
       const data = await response.json()
 
       if (data.success) {
@@ -156,13 +166,13 @@ export default function AdminMatchesPage() {
                       )}
                     </td>
                     <td className="px-6 py-4 whitespace-nowrap text-sm text-gray-900">
-                      {match.team1P1.name} & {match.team1P2.name}
+                      {match.player1P1?.name} & {match.player1P2?.name}
                     </td>
                     <td className="px-6 py-4 whitespace-nowrap text-sm font-medium text-gray-900">
                       {match.team1Score}
                     </td>
                     <td className="px-6 py-4 whitespace-nowrap text-sm text-gray-900">
-                      {match.team2P1.name} & {match.team2P2.name}
+                      {match.player2P1?.name} & {match.player2P2?.name}
                     </td>
                     <td className="px-6 py-4 whitespace-nowrap text-sm font-medium text-gray-900">
                       {match.team2Score}