bug(windows): Key processing with text selection problems (non-compliant app)

The test cases for the [Text Selection and Key Processing spec](https://github.com/keymanapp/keyman/issues/9073) with a legacy app on Windows 10 show some limitations.

See [here](https://github.com/keymanapp/keyman/issues/9073#issuecomment-1801356344) for the test cases and the [google doc](https://docs.google.com/spreadsheets/d/1NDO82y77C45pw_ZcMPcD36NZ4VUy9hQcuByieyeJVtM/edit?usp=sharing) for the test results.

Keyman 16.0.142
Windows 10.0.19045
Google Chrome 119.0.6045.124

## Failed tests

~1. (T02) `^⁞X the quick brown fox⁞` in doc. Typing `BKSP`, then `A`.
Expected result: `Â⁞`
Actual result: `^A⁞`
2. (T04) `^⁞X⁞` in doc. Typing `A`.
Expected result: `Â⁞`
Actual result: `^A⁞`
3. (T05) `^⁞X the quick brown fox⁞` in doc. Typing `A`.
Expected result: `Â⁞`
Actual result: `^A⁞`~
4. (T07) `^⁞X⁞` in doc. Typing `BKSP`, `BKSP`.
Expected result: `foo⁞`
Actual result: `⁞`

**Edit 2025-04-24:** updated T02, T04, T05 because selecting the text causes us to loose the context, so the result we got is correct.