Update .po files to preserve translations when adding %$ conversion specifier

[Copilot]

• Update all backend .po files to include %$ in the msgid for file name validation message
• Update corresponding msgstr translations to include %$ where applicable
• Test the changes to ensure translations still work correctly
• Fix translations that were missed by the initial automated update
• Fix inconsistent trailing period in Spanish translation
• Revert unwanted .pot file regeneration that added line breaks (project uses --no-wrap)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

[MichaIng]

@copilot
Well done, I am glad you found and updated as well the translations where these %v parts were not at the end of the whole string.

But please revert commit d118e7a. We intentionally avoid the line breaks, adding --no-wrap to xgettext and msgmerge. They do compile well, including msgfmt to generate the .mo files (which is done via CI and Weblate, no need to do manually).

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Can you clarify where exactly this happened? I do not see anything in this regards in the agent session log, and all requested changes have been successfully applied.

[Copilot]

@copilot
Well done, I am glad you found and updated as well the translations where these %v parts were not at the end of the whole string.

...

Reverted the .pot file regeneration that added line breaks. The file now maintains the --no-wrap format as intended while still including the %$ conversion specifier.

Commit: 67bb98e