[Feat] Make periodic update (translations) use different branch for main and backport

[echoix]

Is your feature request related to a problem? Please describe.

Currently the workflow that updates the translations opens a PR with a fixed named branch, so only one of these PRs can be open at a time.

Describe the solution you'd like
Be able to have different branches keeps translations up to date without force pushes.

The action opening the PRs might already have a solution for this.

The important thing is to keep the same prefix, as there are some branch creation rules that prevent creating some branches in the main repo.

Also, we might by want to change the schedule a bit.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features
you've considered.

Additional context
At least have the changes on the main branch, as the 8.5 will continue to use the same branch name as before. But backporting could be nice, as we are still using it.

Other enhancement I would like: When I created the workflow, we initially decided to only create the PR if any of the files had more changes than only the date in the header. It was a bit harder than only stage the files that had more changes than just the header. The justification was that we would know that that template was up to date as of that date. However, this ends up creating some churn when the .po files gets synced: we might have 30 or 60 files that get updated with nothing but the date, hiding the last 30 files that have some changes. Lazy loading on mobile means scrolling down takes some time, and annoys me a bit.

[ayushjariyal]

Hi @echoix, I’d like to work on this issue.

My understanding is that the workflow currently uses a fixed branch name, preventing multiple periodic update PRs from existing at the same time. I’m planning to generate the branch name dynamically using ${{ github.ref_name }}.

Does this approach sound correct?