🔧 config: Refactor Twitter & Telegram Actions

[KartikSoneji]

Adds a custom js script to directly call the telegram api and send/pin messages.
Fixes issues with the markdown formatting.
Combines 4 github workflows into one.

• Closes Telegram messages #2
• Closes Use containers for actions #21
• Closes Merge telegram and twitter actions #22

[SirusCodes]

@KartikSoneji is this ready for review?

[KartikSoneji]

@KartikSoneji is this ready for review?

Yes, unless we are planning to shift to WhatsApp Communities.

[SirusCodes]

Yes, unless we are planning to shift to WhatsApp Communities.

We haven't finalized anything like that but until then I guess we can merge it.

[KartikSoneji]

Yes, unless we are planning to shift to WhatsApp Communities.

We haven't finalized anything like that but until then I guess we can merge it.

OK, I still have to add the wait action and push back the starting times.

[SirusCodes]

@KartikSoneji still working on it?

[HarshKapadia2]

Hey @KartikSoneji I just remembered that there have been lots of cases (two in just the past two weeks) where the summary was delayed or there was some other issue, which made us have to run specific message workflows again. If we combine all message workflows in one workflow, we will lose the granular control that we currently enjoy. How do you think we should tackle this?

[KartikSoneji]

@HarshKapadia2 I think this should still allow the same flexibility.

catchup/.github/workflows/send-messages.yaml

Lines 9 to 23 in aab8230

	workflow_dispatch:
	inputs:
	message-template:
	type: choice
	required: true
	default: automatic
	options:
	- automatic
	- reminder
	- joining
	description: |
	Which message template to use.
	if set to `automatic`, resolves to:
	`joining`, if time is after 10pm on Saturday (IST)
	`reminder`, otherwise

[HarshKapadia2]

@KartikSoneji this looks good to me and thank you SO much for this amazing Pull Request, but please just give this a cursory glance and then merge it if everything seems okay to you.

This makes me think, is there is way to check such CI/CD workflow changes before merging? Is building a separate testing environment the only answer?

[tusharnankani]

Nudging @KartikSoneji 🥰

[HarshKapadia2]

With upcoming changes to the Twitter API, what should we do?

Should we move this conversation to a an issue or a discussion?

[tusharnankani]

Let's move to an issue.

[SirusCodes]

@KartikSoneji any updates?

[HarshKapadia2]

This looks good to me. I'm going to merge it. Thank you so much, @KartikSoneji!