Update and expand localized strings for handheld and Wear OS

[daedaevibin]

• Added translations for German (DE), Spanish (MX), Japanese, and Korean.
• Reorganized and updated locale qualifiers for French, Italian, and Russian.
• Updated localized resources to reflect the app name change to PixelPlayer.
• Added feature-specific strings for AI integration, Watch transfer, and Backup/Restore.
• Synchronized Wear OS translations with handheld components.

[daedaevibin]

I think I got all of them..
So many files.

---

I'll double-check translations and inform you when I am fully done.

---

Status: All seems correct.

[daedaevibin]

Package	From	To
io.netty:netty-common	4.2.12.Final	4.2.13.Final
io.netty:netty-handler	4.2.12.Final	4.2.13.Final
io.netty:netty-codec-http	4.2.12.Final	4.2.13.Final
io.netty:netty-codec-http2	4.2.12.Final	4.2.13.Final
com.android.application	9.2.0	9.2.1
com.android.test	9.2.0	9.2.1
com.android.library	9.2.0	9.2.1

---

Bumps netty from 4.2.12.Final to 4.2.13.Final.
Updates io.netty:netty-common from 4.2.12.Final to 4.2.13.Final

[rebornlokii]

❗ Localization Regression Report (French / Italian / Russian)

🧪 Summary of Testing

As the French and Italian localization maintainer, I tested this PR and found no functional improvements.

Instead, it introduces a regression affecting localization support.

---

🚨 Current Issue

The PR breaks French, Italian, and Russian localization.

What changed:

• Several locale-specific values-* resource folders were removed
• This prevents the app from resolving localized resources correctly
• The system falls back to English strings regardless of selected language

---

👀 Observed Behavior

• Language selection in the UI still works
• However, string resources do not reflect the selected locale
• English is consistently used as the fallback output

---

🧠 Likely Cause

This appears to be a misunderstanding of Android's resource localization system.

Removing values-fr, values-it, values-ru, etc. breaks the expected resource resolution chain, forcing default locale fallback.

---

🛠️ Recommendation

To resolve this:

• Either revert the deletion of locale-specific values-* folders

OR

• Reintroduce them with a proper migration plan that ensures:
  • No loss of existing translations
  • Correct fallback behavior per locale
  • Preservation of full localization coverage

---

⚠️ Conclusion

This change currently degrades localization functionality and effectively disables non-English resource resolution.

A rollback or fix is recommended before continuing development on this branch.

[daedaevibin]

@rebornloki-dev

Could you explain exactly what got "removed" ??

As on my end, there are values folders for each of the mentioned languages.

It's potentially the fact I could've forgotten to include them in a file somewhere, but they exist on my end.

They however, do exist. I did removed strictly incomplete ones, and replaced some with correct local folders instead of the generalized names I had seen.

---

Nevermimd, I see what happened.

I'll get on that soon, my apologies. (I was supposed to have copied all the folders but there was a lot more going on at one time with some unpushed changes I made.)

[daedaevibin]

@theovilardo @rebornloki-dev

Cleared up that issue, added russian into the translations (since it already existed but was missing translations) and cleaned up some warnings and errors.

Unsure as to why workflows fail on your end, they all ran fine on my side as well as building it directly.

[daedaevibin]

Note: apologies for the late responses and fixes.

This is my first time dealing with this.. particular.. structure of files for translations (seperate xml files and folders) in comparison to large files with all the different items in one place like I am used too (i18n for web items and such).