Refactor: Replace Custom Events with Filter Queries

[JumpLink]

The Telegram Bot uses grammY, which is a Telegram Bot Framework.

Currently, the internal Telegram Bot events are split into several events using a own implementation via EventService.emitDetailedEvents. If, for example, the event callback_query:data:show-callout-slug:my-callout is triggered, this method ensures that several events are generated:

• callback_query
• callback_query:user-123456789
• callback_query:data
• callback_query:data:user-123456789
• callback_query:data:show-callout-slug * callback_query:data:show-callout-slug
• callback_query:data:show-callout-slug:user-123456789
• callback_query:data:show-callout-slug:my-callout
• callback_query:data:show-callout-slug:my-callout:user-123456789

This allows you to listen for the event that is most suitable for you at the moment.

What I saw too late is that grammY already has its own solution for this, which is also much more powerful, namely so-called Filter Queries. We should refactor the bot so that the custom implementation can be removed and should use Filter Queries instead.