feat(telegram): add support for message_thread_id

[yegle]

Reference: https://core.telegram.org/bots/api#sendmessage

closes #361

[codecov]

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.03 🎉

Comparison is base (048e61a) 78.92% compared to head (01ad967) 78.95%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #362      +/-   ##
==========================================
+ Coverage   78.92%   78.95%   +0.03%     
==========================================
  Files         101      101              
  Lines        4431     4438       +7     
==========================================
+ Hits         3497     3504       +7     
  Misses        756      756              
  Partials      178      178              

Impacted Files	Coverage Δ
pkg/services/telegram/telegram_json.go	94.28% <100.00%> (+1.42%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[piksel]

Looks good, but there are no tests. Also, how do you retrieve the thread ID?

[yegle]

Test added, info on how to obtain the message_thread_id added.

[piksel]

Great work! I'm not sure how I feel about linking a SO question in the docs, but perhaps it's better than nothing. We could always update the docs at a later time.

[yegle]

Is it okay to keep the $chat_id:$message_thread_id format? I only proposed it because it's easy to implement, but we can change to something more formal.

[piksel]

Yeah, I think it's a good way to do it. Normally I would prefer to add another parameter, but since this is directly relating to a target it makes sense to use this. It also doesn't need to be escaped which is a plus!

[instantdreams]

Documentation needs to be updated to reflect use and examples of Topic ID