feat: add translations workflow for GitHub releases

[kbdharun]

No description provided.

[SethFalco]

Take a peek at the CONTRIBUTING guide:

https://github.com/tldr-pages/tldr-translation-pairs-gen/blob/main/CONTRIBUTING.md#backward-compatibility

It's cool if we create new assets, but preferably, we shouldn't change how we package the original artifacts.

TL;DR: Makes sense, but can we add the new artifacts instead of replace the existing artifact.

[kbdharun]

It's cool if we create new assets, but preferably, we shouldn't change how we package the original artifacts.

Agreed, I will separate this workflow and we can continue to have the existing one that way the GitHub page would be present and we can upload the ZIPs to releases for ease of downloading and redistributing in places like Kaggle.

Edit: Done

[SethFalco]

LGTM!

Fine with this overall, but perhaps the CSV dataset should have CSV in the name similarly to the others for consistency?

That way when someone reviews the releases, users just know it's CSV rather than having to guess what the unspecified format contains.