The message length limit is not respected when sending messages to the logging chats

[denyshon]

Describe the bug
The message length limit (1-4096 characters after entities parsing) is not respected when sending messages to the logging chats, possibly causing extra exceptions.

To Reproduce
Steps to reproduce the behavior:

1. Generate an error with a long enough traceback that is sent to the logging chats.
2. See the console and the logging chats.

Actual behavior
No messages are sent to the logging chats. Extra exceptions are raised and printed to the console when trying to send messages to the logging chats.

Expected behavior
The error message is sent to the logging chats. No extra exceptions are raised.

Additional context
To fix this, we need to either avoid including traceback in Telegram messages when it's too long, or split the message into several parts (while keeping the formatting).

[denyshon]

Adding priority-low since it's a rare case, and only administrators are affected