Issues related to direct keyboard input.

@bitbound is already working on this.

Since Jul 21, 2023.

This issue will represent all issues related to direct keyboard input, especially from keyboards other than en-US.

Starting with release [2023.07.20.1533](https://github.com/immense/Remotely/releases/tag/v2023.07.20.1533), I've made an attempt to support other keyboards and languages. I've only been able to test using the on-screen keyboard, though, so please comment here with any issues you're encountering in the latest release.

The above release also had the following changes:
- Fixed an issue where certain special characters on the en-US keyboard wouldn't go through when using "Type Clipboard" function from the menu.
- Highlighting text with Shift + Arrow Key, Shift + Home, and Shift + End now works.
- Key combos involving Win key (e.g. Win + R), however, still do not work.
- Unlike a native desktop app, the browser isn't able to intercept the keypress and stop it from propagating to the host machine. This presents challenges in sending key combos involving Win. This isn't super high priority at the moment, but I might take another stab at this later.

Related Issues:
#673
#656
#621
#464
#396
#369
#294

Edit: @dkattan brought to my attention the [Keyboard.lock](https://developer.mozilla.org/en-US/docs/Web/API/Keyboard/lock) method. I have reservations about bringing it in due to having been in "experimental" state since 2018, not working on Firefox, and requiring full-screen to be active. Personally, I hardly ever use full-screen. But if you feel strongly one way or another about using this, let me know in the comments.

Expanding on my concerns about experimental features. It wouldn't be hard to implement this so it only works on Chrome/Edge. However, experimental/prerelease features (in general, not just JavaScript) are subject to frequent, breaking API changes. Individually, it's usually not difficult to refactor when the breaking change happens. But if we habitually add experimental dependencies, the risk begins to compound, especially if we don't have tests in place to cover them. I also feel there should be a hard limit or explicit criteria for bringing in non-standard features to put a cap on the maximum potential risk of breakage. So far, that criteria has just been in my head, and I'm somewhat risk-adverse.