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/calendar-sync/calendar-sync.handlers.ts

@@ -35,6 +35,20 @@ export class CalendarSyncEventHandlers {
     await this.calendarSync.enqueueIn(tx, 'TREATMENT', event.aggregateId);
   }
 
+  // The same events, a second entry: the withdrawal span of the treatment.
+  // Enqueued also when the treatment has no withdrawal days (any more): the
+  // worker then removes an event created earlier.
+  @OnDomainEvent(
+    ['TreatmentRecorded', 'TreatmentCorrected'],
+    'calendar-sync.withdrawal',
+  )
+  async withdrawal(
+    event: AnyDomainEventEnvelope<'TreatmentRecorded' | 'TreatmentCorrected'>,
+    tx: Prisma.TransactionClient,
+  ): Promise<void> {
+    await this.calendarSync.enqueueIn(tx, 'WITHDRAWAL', event.aggregateId);
+  }
+
   @OnDomainEvent(
     ['FeedingRecorded', 'FeedingCorrected'],
     'calendar-sync.feeding',