8642: Adding "Build Crowdin Translation Packages" workflow

[BenedekFarkas]

Fixes #8642

Successful job execution for commit 498e0c6: https://github.com/OrchardCMS/Orchard/actions/runs/4489388067/jobs/7895144432

Successful job execution for commit 6fc93f4: https://github.com/OrchardCMS/Orchard/actions/runs/4491534994/jobs/7900123857

[andrii-bodnar]

Hey everyone,

just accidentally noticed this PR. I highly recommend not using the API v1. It's deprecated and it's going to be removed. Please use the API v2 - https://developer.crowdin.com/api/v2/

in addition, I'd recommend the following GH Actions that might simplify your workflow and make integration with Crowdin much easier:

• https://github.com/crowdin/github-action
• https://github.com/andrii-bodnar/crowdin-request-action

[BenedekFarkas]

@andrii-bodnar thanks for the recommendation, I'll check it out!

[andrii-bodnar]

@BenedekFarkas please note that the build in API v2 is an asynchronous process so it will require more API calls to do it.

Here is an example of such a case - https://github.com/andrii-bodnar/crowdin-request-action/blob/main/EXAMPLES.md#build-project-translations (if to use the crowdin-request-action. In case of Crowdin GH Action it already under the hood)

[BenedekFarkas]

Thanks Andrii, the async call will be fine for now, because the projects have very little activity, so this is about keeping them up-to-date, just in case.

[andrii-bodnar]

@BenedekFarkas do you just need to build the projects and the translations download happens somewhere else?

[BenedekFarkas]

@andrii-bodnar downloading the packages is completely independent, because the translations are publicly available, so anyone can just grab any language package they want.