fix(matchService): handle missing match after update with HttpError

- Added error handling in MatchService to throw an HttpError if a match is not found after an update, improving robustness.
- Enhanced sorting logic in DiaryView to ensure case-insensitive comparison for first and last names, with a stable fallback using IDs.
- Refactored currentClub watcher in ScheduleView to use an object syntax for better clarity and immediate execution on initialization.

backend/services/matchService.js

@@ -12,6 +12,7 @@ import Club from '../models/Club.js';
 import SeasonService from './seasonService.js';
 import { checkAccess } from '../utils/userUtils.js';
 import { Op } from 'sequelize';
+import HttpError from '../exceptions/HttpError.js';
 
 import { devLog } from '../utils/logger.js';
 class MatchService {
@@ -470,6 +471,9 @@ class MatchService {
 
         // Aktualisiertes Match nochmals laden und für WebSocket-Broadcast anreichern (gleiche Struktur wie getMatchesForLeague)
         const updated = await Match.findByPk(matchId);
+        if (!updated) {
+            throw new HttpError('Match not found after update', 404);
+        }
         const enriched = {
             id: updated.id,
             date: updated.date,