Verbose-log overflow chunks are re-sent (not edited) when a job retries

[miridius]

Symptom

In verbose mode, when a job's log output exceeds Telegram's 4096-char per-message limit, LogMessage splits it across multiple messages. When that job retries, only the first message is seeded and edited on the retry — the continuation chunk(s) are re-sent as new messages on each attempt instead of editing the ones already posted.

Repro

1. Trigger a verbose-mode job whose accumulated log exceeds 4096 chars (so it splits into 2+ messages).
2. Make the job fail transiently so the queue retries it.
3. Observe: on each retry the first message is edited in place, but the continuation chunk(s) appear as fresh duplicate messages.

Scope

Verbose mode only — non-verbose logs don't approach the 4096-char limit.