Handle properly Bad Request: group chat was upgraded to a supergroup chat

[johnd0e]

After adjusting the admin group settings, I encountered a problem: after successfully banning someone in the main group, there was no message in the admin group, but instead, I received this log entry:

2024/10/15 13:25:26.651 [WARN]  {events/admin.go:50 events.(*admin).ReportBan} failed to send admin message, can't send message to telegram "**permanently banned [{1480342322  Маргарита Ершова}](tg://user?id=1480342322)**\n\nИщу людей, возьму 1-4 человека 20+ Удаленная деятельность. От 75$ в день. Кому интересно: Пишите + в сообщения\n\n": Bad Request: group chat was upgraded to a supergroup chat

The issue arose because the group was unintentionally converted to a supergroup, resulting in a change of its id. This was not my fault, as Telegram does this automatically without notifying users.

However, this kind of error could be handled more gracefully, as the error response contains all the necessary information:

{
"ok": false,
"error_code": 400,
"description": "Bad Request: group chat was upgraded to a supergroup chat",
"parameters": {
"migrate_to_chat_id": -1001432162429
}
}

It would be beneficial if the bot could handle the error smoothly and then politely request that the id be updated in the settings.

Additionally, it would be helpful for the bot to acknowledge messages in unrelated groups by responding that it is not configured to process messages from the group id=xxx.

[johnd0e]

Cannot agree to see this issue as an "Idea".

This is the problem, that the next tg-spam user will be googling. And the next.
Easily avoidable.