fix: improve message handling by using senderID for identification

[cointem]

修复了pkg/channels/telegram.go文件夹下handleMessage方法校验senderID不一致的bug。
** 第一次校验senderID **

** 第二次调用HandleMessage也应该传senderID进行校验 **
旧代码：

新代码：

[cointem]

refs #310

[Copilot]

Pull request overview

This PR fixes a bug in the Telegram channel where the senderID used for initial allowlist validation was inconsistent with the senderID passed to HandleMessage. The senderID variable can include both the user ID and username (format: "ID|username"), but the old code only passed the numeric user ID to HandleMessage, causing potential authorization issues when usernames are used in the allowlist.

Changes:

• Fixed inconsistent senderID usage in handleMessage by passing the senderID variable (which may include username) instead of just the numeric user.ID
• Added a blank line between Start() and Stop() methods for consistent formatting

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Leeaandrob]

@Zepan Uses senderID instead of chatID for message identification — ensures correct attribution in group chats.

Recommendation: Merge. +2/-1, trivial but important for multi-user scenarios.