fix: use UMO-bound config for group_icl_enable in on_message

[saschabuehrle]

Fixes #7305

on_message() currently reads group_icl_enable from the default config via self.context.get_config().
When a platform instance is bound to a non-default profile, this can disable group context recording even though ltm_enabled() correctly reads the UMO-bound config.

This patch makes on_message() read group_icl_enable with the same umo=event.unified_msg_origin lookup path used by ltm_enabled().

Greetings, saschabuehrle

Summary by Sourcery

Bug Fixes:

• Fix reading of group_icl_enable in on_message to respect UMO-bound configuration instead of always using the default profile.

[sourcery-ai]

Hey - I've left some high level feedback:

• When switching get_config to use umo=event.unified_msg_origin, consider guarding against missing or partial config (e.g., using .get with sensible defaults) to avoid runtime errors if the UMO-bound profile lacks provider_ltm_settings or group_icl_enable.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- When switching `get_config` to use `umo=event.unified_msg_origin`, consider guarding against missing or partial config (e.g., using `.get` with sensible defaults) to avoid runtime errors if the UMO-bound profile lacks `provider_ltm_settings` or `group_icl_enable`.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request updates the configuration retrieval in the on_message method to include the unified message origin (umo). The reviewer suggests optimizing performance by fetching the configuration once at the beginning of the method to avoid redundant lookups across multiple calls.

[gemini-code-assist]

The configuration for the current UMO is fetched multiple times in this method (via ltm_enabled, need_active_reply, and again here). While this PR correctly fixes the UMO binding, consider fetching the configuration once at the beginning of on_message and reusing it to avoid redundant lookups and improve efficiency.