[Bug]: Android device.input.type fails on characters such as ':'

Finding: In an external report against Playwright 1.64.0 (https://github.com/microsoft/playwright/issues/43259), Android device.input.type('Sara:30') throws "No mapping for : found" before any character is sent. The reporter used a macOS host (Node 25.9.0) with an Android 17 emulator or device. This is an external report only; KFA did not reproduce it and the repro script was not run here. Reported behavior: letters, digits, spaces and % type correctly according to the reporter, but a string containing ':' fails. The reporter says the failure is not tied to a particular app, package name or screen size, and that any other character typed with Shift would fail the same way on every Android device. They state that device.input.press for a named key still uses the key map and is not affected, so device.input.type is the only method reported as affected (https://github.com/microsoft/playwright/issues/43259). Reporter's hypothesis, not maintainer-confirmed: inputType in packages/playwright-core/src/server/dispatchers/androidDispatcher.ts builds one inputPress per character, upper-cases each character and looks it up in an Android key-code map. ':' is Shift+semicolon and has no entry. The reporter also says mapped characters are pressed with Promise.all, so their order is not guaranteed (https://github.com/microsoft/playwright/issues/43259). Status: the issue is open with no comments and no maintainer response in the supplied data. The reporter says they intend to work on it. No fix commit, pull request or released fix is supplied, so the fix status is unfixed or unknown. No workaround is documented in the source. Actionable diagnosis, source-backed only: if you see "No mapping for : found" from device.input.type, check whether the string contains Shift-typed characters such as ':'. Treat this as a likely match to the reported issue, not a confirmed cause. Affected versions other than 1.64.0 are unknown.