fix(gateway): show Telegram context compaction notice

[guinnessmax]

Summary

Telegram currently suppresses the context compaction lifecycle status as gateway noise:

r"|compacting\\s+context\\s+[—-]\\s+summarizing\\s+earlier\\s+conversation"

That means long gateway turns can silently pause while Hermes summarizes older conversation history. From the user's perspective, especially in Telegram, this looks like the bot is stuck or has lost context.

This matches the concern raised in #16469: users have no signal when context is auto-compressed / summarized.

User-visible impact

• A long Telegram session pauses during context compaction.
• Hermes emits a lifecycle status like:

🗜️ Compacting context — summarizing earlier conversation so I can continue...

• The Telegram gateway filters it out via _TELEGRAM_NOISY_STATUS_RE.
• The user sees silence instead of an explanation.

Suggested fix

Do not classify the compaction lifecycle message as Telegram noise. Keep filtering noisy auxiliary/retry/provider chatter, but let this one status through.

Local verification

UV_PROJECT_ENVIRONMENT=.venv-codex uv run --extra dev python -m pytest tests/gateway/test_telegram_noise_filter.py -q
.......                                                                  [100%]
7 passed in 1.25s

[teknium1]

Closing — routine compaction is silent by design on chat surfaces: the noise regex this PR deletes from now gates every chat platform fail-closed (widened beyond Telegram by #39293), so removing the compacting context pattern would un-silence every gateway, not just Telegram. Failure notices and manual /compress feedback are the deliberate carve-outs from that silence.

The right vehicle for what you want is #52995 — an opt-in, default-off progress notice. If that gets a maintainer yes, a reshaped version of this PR behind that flag would be welcome.