feat(alerting): Added the ability to send messages to Telegram topics…

[medaved]

Summary

• Added the ability to send messages to Telegram topics in groups.

Checklist

• Tested and/or added tests to validate that the changes work as intended, if applicable.
• Updated documentation in README.md, if applicable.

[TwiN]

Hey, just so you know, I'm currently working on #929, which may also implement what this PR is implementing.

[medaved]

@TwiN how can i help with this?

[TwiN]

Hey, sorry about this, I'm going to close this because I've been working on adding support for provider overrides at the alert level, and this impacts how overrides in general work. The good news is that you'll be able to override the topic parameter with this change, making this PR no longer necessary.

I am, however, very thankful for your contribution!

[0n1cOn3]

Hey @TwiN

I don't see any connection here. Telegram Topics have nothing to do with the endpoints per se. But rather that support for topics is introduced here. It would make notifications a lot easier to handle and would no longer clutter up the main chat. Please take another look at this PR :)

[TwiN]

@0n1cOn3 oh crap, you're completely right. I went through the files changes way too quickly, saw green and overrides & assumed it was the change 🤦‍♂️

[medaved]

@TwiN PR refreshed, because old commit had conflicts

[TwiN]

@medaved Some tests are failing

# github.com/TwiN/gatus/v5/alerting/provider/telegram [github.com/TwiN/gatus/v5/alerting/provider/telegram.test]
Error: alerting/provider/telegram/telegram_test.go:159:32: unknown field ID in struct literal of type AlertProvider
Error: alerting/provider/telegram/telegram_test.go:159:43: unknown field TopicId in struct literal of type AlertProvider

[medaved]

@TwiN broken tests were fixed