Fix appeal flow wiring: incidents + restriction messages

[ForeverInLaw]

Summary

Two fixes so the appeal flow actually works at runtime.

• AuditService never wired — runtimeAssembly set Web.AuditService but never the top-level AuditService field, so makeTelegramListener's if a.AuditService != nil was always false. Result: IncidentCreator was never attached to the listener, no audit incident was created from the moderation pipeline, and ensureIncident always returned 0 — so the "Обжаловать" button was never attached to warn/ban messages. Wired AuditService: auditSvc into the assembly struct (pre-existing bug, surfaced by the appeal feature).
• Restrictions got no group message — postBanGroupMessage skipped pc.outcome.Restrict, so temporary mutes (early strikes, soft-ban mode) posted no group message and no appeal button. It now posts for restrictions too, with text 🔇 Пользователь ограничен за спам (vs 🚫 Пользователь забанен за спам for a permanent ban). Still skipped for channel bans and dry/training runs.