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/test/winter-checks.e2e-spec.ts

@@ -203,7 +203,12 @@ describe('Winter checks (e2e)', () => {
       'ColonyStatusChanged',
       'ColonyEnded',
     ]);
-    expect(events[1].payload).toEqual({ status: 'DECEASED' });
+    expect(events[1].payload).toEqual({
+      status: 'DECEASED',
+      endedOn: '2002-03-20',
+      releasedQueenId: null,
+      via: 'WINTER_CHECK',
+    });
     expect(
       await prisma.domainEvent.count({ where: { aggregateId: survivorId } }),
     ).toBe(0);