Update in-repo translation source files

[github-actions]

Run lupdate with arguments -no-obsolete

[cbjeukendrup]

@RomanPudashkin I have some reservations about putting strings in the global context:

• When one occurrence has an extra comment, like here, that comment is of course only relevant for that single occurrence, but if all occurrences appear as one string on Transifex, that's problematic of course
• Ensuring consistent translations across the app is not our task. That's the task of the translators, and Transifex has plenty of tools to assist in that.
• On the contrary: in different places, the same string may need different translations, so we need to give translators the ability to do that.
• Because Transifex automatically fills in translations for other occurrences of the same string in different contexts if the translator doesn't do that themselves, having multiple occurrences of the same string does not create more work for translators.
• In the list of all strings on Transifex, the strings are sorted in such way that strings that appear close to each other in the code are listed close to each other. So, if you have a dialog, all strings in that dialog are listed close to each other, but if there's one button in the dialog whose text is in the global context, the text of that string will be in a totally different place in the list, making it more difficult to keep the overview.

[Jojo-Schmitz]

Wouldn't these changes need to get pushed to Transifex?

[cbjeukendrup]

Ah yes, done!