[Infra] Wire Discord Logger into Engine and Offboarding Microservices

[aaron-iz]

Adds Discord logging to the Chronos.Engine and Chronos.Offboarding worker services, matching the existing setup in Chronos.MainApi. Both services already had transitive access to the Discord logger through Chronos.Shared (via Chronos.Data), but never wired it up — they were only logging to the console.

Changes

src/Chronos.Engine/Program.cs

• Added using Chronos.Shared.Logging
• Configured DiscordLoggerConfiguration from the DiscordLogger config section
• Registered the Discord logger with bot name "ChronosEngine"

src/Chronos.Offboarding/Program.cs

• Added using Chronos.Shared.Logging
• Configured DiscordLoggerConfiguration from the DiscordLogger config section
• Registered the Discord logger with bot name "ChronosOffboarding"

src/Chronos.Engine/AppSettings/appsettings.json

• Added DiscordLogger.DiscordWebhookUrl configuration placeholder

src/Chronos.Offboarding/AppSettings/appsettings.json

• Added DiscordLogger.DiscordWebhookUrl configuration placeholder

Configuration

Both services read the webhook URL from:

• appsettings.json: DiscordLogger:DiscordWebhookUrl
• Environment variable: DiscordLogger__DiscordWebhookUrl

If the webhook URL is empty, the logger falls back to console-only logging (no Discord messages are sent), so this is fully backward-compatible.

Deployment Note

To enable Discord logging for these services in the deployed environment, add DiscordLogger__DiscordWebhookUrl=<url> to the .engine.<CLOUD_ENV>.env and .offboarding.<CLOUD_ENV>.env files in Chronos.ServiceProxy.