Wrong keyboard layout converter — instantly fix mistyped text in any language

### Description of the new feature / enhancement

A universal tool that detects when text was typed using the wrong keyboard layout and converts it to the intended characters. The user selects any mistyped text, presses a configurable shortcut, and the text is instantly replaced in-place with the correct characters — based on physical key position mapping between any two layouts. Works across all supported language pairs, in any text field or application.

### Scenario when this would be used?

A bilingual user switches frequently between two languages — say Hebrew and English, Russian and English, Arabic and French, or any other pair. They begin typing in one language while the keyboard is set to the other. Instead of their intended text they get a garbled string: Руддщ instead of Hello, or ùìåí instead of שלום, or ghsghs instead of صحيح.

Rather than deleting everything and retyping, the user selects the garbled text, hits the shortcut (e.g. Ctrl+Shift+Space), and the tool replaces it with the correctly mapped characters — instantly, without leaving the current app or field.

### Supporting information

Why this matters — the real cost of typing in the wrong layout

- Multilingual users — anyone who types daily in two or more languages — misfire constantly. A moment of distraction, a missed layout switch, or an app that doesn't respect the OS language toggle is all it takes.
- The current workaround is: notice the mistake, select all garbled text, delete it, switch layout, retype from memory. For a sentence of 10–15 words this takes 10–20 seconds. A heavy user triggers this dozens of times per day — that's several minutes of pure friction, every day, indefinitely.
- The problem is especially acute for non-Latin scripts (Hebrew, Arabic, Russian, Greek, Thai, etc.) where wrong-layout output is completely unreadable there's no "close enough" to work from. Users in these communities have been patching this with third-party utilities for 20+ years, which is a strong signal of unmet demand.
- For users who write long-form content — emails, documents, code comments — a single wrong-layout paragraph can derail focus entirely. The retype interruption is not just a time cost; it breaks flow.
- This is a near-zero-effort fix from the user's perspective (one shortcut), which makes the contrast with the current experience especially jarring. Once someone uses this feature, not having it feels broken.

The issue names no files, tests, or entry points. Start by locating the existing PowerToys keyboard-related utility and its handling of global shortcuts, then determine the scope of layout mappings and cross-application text replacement. Done would require a defined supported-layout scope, shortcut behavior, and validation across the stated language-pair scenarios.

Written by the indexing model from the issue text.