Send typedCharacter events for Braille when using ToUnicodeEx

[codeofdusk]

Link to issue number:

Closes #10569.

Summary of the issue:

The toUnicodeEx approach of typed character detection doesn't work for Braille keyboards.

Description of how this pull request fixes the issue:

Manually sends typed character events to objects using toUnicodeEx if focused. We must send all keys after they are typed to avoid unintentionally speaking passwords in Windows Console. A new keyboardHandler.shouldUseToUnicodeEx function has been added for this detection.

Testing performed:

Tested that typed characters are reported from a 5th-generation Freedom Scientific Focus keyboard, and that password reporting works as expected.

Known issues with pull request:

None.

Change log entry:

== Bug fixes ==

• On Windows 10 version 1607 and later, typed characters from Braille keyboards are spoken in more situations. (Keyboard handler/ToUnicodeEx: typed characters from Braille displays not reported #10569)

[codeofdusk]

Cc @LeonarddeR @michaelDCurran

[AppVeyorBot]

PR introduces Flake8 errors 😲

See test results for Failed build of commit 3e6b3e27bd

[AppVeyorBot]

PR introduces Flake8 errors 😲

See test results for Failed build of commit b56a23096e