🧑‍💻 (frontend): add placeholder translation to mitigate merge conflicts

[dakshesh14]

Added a placeholder translation entry at the end of each language file to reduce merge conflicts when multiple contributors are working on translations. This change also helps minimize unnecessary diff sizes.
Address: #831

Purpose

Introduce a placeholder translation entry to prevent merge conflicts in translation files and reduce unnecessary diff size during collaborative work.

[lunika]

Hi,
Thanks for your contribution.
All the translation process is automated and for now we didn't have any conflict.

Can you describe a bit how you work and how this lead to a conflict ?

Thank you

[dakshesh14]

Hi, thanks for the clarification. I wasn’t aware that the translation process here is fully automated.

In some other projects I've contributed to, we encountered merge conflicts when multiple contributors added translations to the last line of a language file. Because JSON doesn’t allow trailing commas, adding a new entry requires modifying the previous line to append a comma, which results in unnecessary diffs and occasional merge conflicts. For reference, this commit shows a case where there's an unnecessary diff.

To prevent that, some teams add a placeholder translation at the end of the file—something I adopted in this PR.

That said, if translations here are handled exclusively by automation, this PR might not be necessary. I’m happy to close both the PR and the issue if that’s the case. Thanks again for taking the time to review!

[lunika]

Hi,
Yes I can you can close it.
Thanks