feat: T4b/T4c wave 8 - weather history, phenology, honey chain, Telegram base

- Weather history from Open-Meteo behind an adapter: worker loop
  phenology-weather with backoff, Retry-After, User-Agent, chunked
  writes and forecast-to-archive correction
- Phenology: growing degree sum per DWD, phase from reports, GTS and
  calendar, calibration from previous years, daily job step,
  SeasonService reads the stored state
- Honey chain: prefill for extractions and batches (proposals only),
  plausibility and withdrawal warnings, Extraction lock, chain events
  and batch.created webhook from HoneyBatchRecorded
- Telegram base: schema, NotificationDelivery outbox, hardened bot
  client, startup check without crash, no-network-outside-loops guard
- ARCHITECTURE.md: sections 11.11-11.13, assumptions 42-46, env table

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

ApiCore-Backend/src/telegram/telegram.module.ts

@@ -0,0 +1,17 @@
+import { Module } from '@nestjs/common';
+import { telegramConfig } from './telegram-config';
+import { TELEGRAM_CONFIG, TelegramClient } from './telegram-client';
+
+/**
+ * The Bot API client for the worker's Telegram loops. Reads the token from
+ * the environment once; without it the client reports isConfigured() false
+ * and the loops do not run.
+ */
+@Module({
+  providers: [
+    { provide: TELEGRAM_CONFIG, useFactory: () => telegramConfig() },
+    TelegramClient,
+  ],
+  exports: [TelegramClient],
+})
+export class TelegramModule {}