remove setWebhook since it is already set before

[wochinge]

Proposed changes:

• fixes Telegram channel broken in latest update #4128

Status (please check what you already did):

• made PR ready for code review
• added some tests for the functionality
• updated the documentation
• updated the changelog
• reformat files using black (please check Readme for instructions)

[erohmensing]

Hehe, did you break this from async actions? 😁If so have you checked the other channels to make sure this isn't happening anywhere else?

[wochinge]

Hehe, did you break this from async actions?

yes :-D

If so have you checked the other channels to make sure this isn't happening anywhere else?

The telegram channel is the only one where we set something extra (the webhook). So it should be fine 🎉

[erohmensing]

Awesome, but can we please open this against 1.2.x 😁

[wochinge]

I also could have just changed it. And I have to merge it both in master and 1.2.x

[erohmensing]

Haha ok this is true I'm sorry 😅

[erohmensing]

Do you know if when community members make PRs we can change where they're trying to merge to? Or do we have to ask them to?

[wochinge]

we can definitely ask them to merge to 1.2.x.
Should I also cherry-pick this on master?

[erohmensing]

Yeah just also was wondering if there is an easier way that we can get them to do it without having to ask every time. What do you mean cherry pick, can't you just merge master <--- 1.2.x after we merge it on 1.2.x?

[wochinge]

I mean git cherry-pick <commit hash>. I think the merge to master is only when we create 1.3, but I'd like to have it on master asap for the community member.

[erohmensing]

I thought you always merged changes to the patch branch to master as you do them

[wochinge]

not according to the figure you shared in the Slack channel (would be also too much hassle)