feat: T4 wave 5 - colony end cleanup, withdrawal chain, next steps, inspection takeover UI

- Colony end releases the queen in the same transaction; open
  suggestions become obsolete and a CLEANUP suggestion lists open
  tasks and the queen; apply-cleanup validates evidence and blocks
  reactivated colonies
- Withdrawal chain: plausibility warnings on harvest and bottling,
  conflict notifications also when a treatment is entered or corrected
  after the harvest (naming bottled lots), withdrawal spans in the
  calendar and M365 sync, Berlin-day end events
- Next 3 steps per colony and the "Heute" endpoint with ranking and an
  explicit merge table by intent
- Inspection-triggered rule suggestions follow the colony's latest
  inspection (resolve when the finding is gone, refresh when it stays)
- Frontend: colony card takeover in the inspection form, feed status as
  condition, occupied frames 0-40; legacy offline entries keep syncing
- Notifications and preferences are deleted with their user

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

ApiCore-Backend/src/backup/backup.service.ts

@@ -1057,7 +1057,7 @@ export class BackupService {
         }
         imported.calendarSyncSettings = rowsOf('calendarSyncSettings').length;
 
-        // Keyed by sourceType+sourceId, like CalendarSyncService.enqueue -
+        // Keyed by sourceType+sourceId, like CalendarSyncService.enqueueIn -
         // the target database may already track the same source under
         // another id. graphEventId comes along, so a restored entry keeps
         // updating its existing M365 event instead of creating a duplicate.