feat(i18n): add full Russian localization (ru.i18n.json)

[yearningss]

Description

This Pull Request introduces a comprehensive and polished Russian translation for the application UI (ru.i18n.json).

The primary goal of this update is to move away from literal/machine translations and provide natural, accurate phrasing commonly used by Russian-speaking networks/proxy application users and developers.

Key Changes

• Complete Coverage: Translated all newly added keys across all screens (AboutScreen, SettingsScreen, NetCheckScreen, meta, etc.).
• Context-Aware Terminology: Refined technical terms (e.g., DNS resolution, TUN mode routing, proxy chaining, rulesets) to align with standard networking concepts in Russian UI design.
• Interpolation & References Preserved: Intact preservation of all internal variable placeholders ($p, $p1, etc.) and internal string reference schemes (@:{...}).
• Formatting Standards: Ensured strict JSON validity with appropriate punctuation and hyphen usage according to standard Russian interface guidelines.

Verification

• Verified JSON file structure and key-value mapping.
• Validated that all reference templates (@:{...}) correctly link to existing keys.

---

P.S. Note for reviewers: using standard hyphens in text isn't a sign of "AI slop"—real humans use regular dashes without long Unicode em-dashes too :)

[felowctl]

Dup of #1817. Almost all of the same points are applicable to this PR too. It basically just changes translations that are already pretty good.

Also, according to the points introduced in Wikipedia's article on signs of AI, both the PR message and the commit description were most likely generated by AI as well.

[yearningss]

Dup of #1817. Almost all of the same points are applicable to this PR too. It basically just changes translations that are already pretty good.

Also, according to the points introduced in Wikipedia's article on signs of AI, both the PR message and the commit description were most likely generated by AI as well.

Just to clear things up: I wrote both the PR description and the translations myself - no AI tools were used.
Regarding the decision in #1817: I respectfully disagree with closing this. The reason for these changes comes directly from real feedback: several native speakers (including people who actively use this app) mentioned that the current translation feels awkward, overly literal, and confusing in places.
My PR aims to replace those clunky strings with natural phrasing that actual users find much clearer. If there are specific translations here you disagree with, I'm open to discussing and tweaking them, but I strongly believe updating these lines will improve the overall user experience.

[Xaveliy]

Having participated in editing the previous translation, I carefully reviewed the proposed changes.
Overall, the translation is much improved. There are some points with which I disagree, particularly the use of terms that are not entirely clear to a beginner. For example, "регулярные выражения" have been replaced with "RegExp." While this is a strict translation, it might be better to use "регулярные выражения (RegExp)." This also applies to a number of other terms.
However, such points can be further refined.
Overall, the phrases in the translation have become better, smoother, and shorter, improving the clarity of the translation. I propose accepting this translation as significantly improved.

[yearningss]

Having participated in editing the previous translation, I carefully reviewed the proposed changes. Overall, the translation is much improved. There are some points with which I disagree, particularly the use of terms that are not entirely clear to a beginner. For example, "регулярные выражения" have been replaced with "RegExp." While this is a strict translation, it might be better to use "регулярные выражения (RegExp)." This also applies to a number of other terms. However, such points can be further refined. Overall, the phrases in the translation have become better, smoother, and shorter, improving the clarity of the translation. I propose accepting this translation as significantly improved.

Thank you very much for the detailed feedback! I really appreciate you taking the time to review the translation.

Could you please point out exactly which parts you think could be improved or where the terminology might be unclear for beginners? I’ll be happy to revise those parts. I’m always willing to learn and improve my approach to make the translation more accurate and accessible.

[Xaveliy]

In fact, it's easier for me to create a combined, compromise version based on your and my translations. This can be done in various ways, but first, we need your consent. Proposing and discussing changes one by one will drown us.

[yearningss]

In fact, it's easier for me to create a combined, compromise version based on your and my translations. This can be done in various ways, but first, we need your consent. Proposing and discussing changes one by one will drown us.

Yeah, I’m fine with combining them. I agree that we don’t need to discuss every single change separately - let’s just make a reasonable compromise version.

[Xaveliy]

Then I'll start preparing such a file. It'll take quite a while. I'll get the source from your repository. How do I send you the intermediate results?

[Xaveliy]

I've created a compromise translation file. If you'd like, I'll submit a pull request. Or you can take a look at it first. My email address is here, just in case - v.pupkin3012@gmail.com