feat(events): migrate game-creation and bot flows to Redis Streams

Replace synchronous account→core game-creation HTTP call and plain
pub/sub bot game-start events with Redis Streams using consumer groups,
XACK, retry, and a Dead Letter Queue for at-least-once delivery and
observability.

- account: GameCreationStreamClient publishes game-creation requests and
  correlates responses via a per-instance consumer group (NCS-91)
- core: GameCreationStreamListener consumes requests, calls
  GameCreationService, publishes response events, retries, and routes
  exhausted/unparseable events to the DLQ (NCS-91, NCS-93, NCS-94)
- official-bots: bot game-start events migrated from pub/sub to Streams
  with consumer group, XACK, retry, and DLQ (NCS-92)
- account EventPublisher dual-writes to the stream and legacy pub/sub
  channel for backward compatibility
- all flows use the typed EventEnvelope (eventId/type/payload/timestamp/
  correlationId) with DLQ error context (eventType, error, attempt)
- register new DTOs and EventEnvelope/EventType for native reflection

Closes NCS-91, NCS-92, NCS-93, NCS-94

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

modules/api/src/main/scala/de/nowchess/api/dto/GameCreationRequestDto.scala

@@ -0,0 +1,10 @@
+package de.nowchess.api.dto
+
+import de.nowchess.api.game.GameMode
+
+final case class GameCreationRequestDto(
+    white: Option[PlayerInfoDto],
+    black: Option[PlayerInfoDto],
+    timeControl: Option[TimeControlDto],
+    mode: Option[GameMode] = None,
+)

modules/api/src/main/scala/de/nowchess/api/dto/GameCreationResponseDto.scala

@@ -0,0 +1,6 @@
+package de.nowchess.api.dto
+
+final case class GameCreationResponseDto(
+    gameId: Option[String],
+    error: Option[String] = None,
+)