fix(input): Removed batching of move events of PEN_PACKET

[aceradryd]

Description

The changes ensure that move events from pens are no longer batched.
This is necessary when Sunshine is used to work with graphics programs.

Issues Fixed

moonlight-stream/moonlight-android#1427

Associated pull requests

moonlight-stream/moonlight-common-c#99

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)

• src/input.cpp: Language not supported

[cgutman]

When I was testing the the pen support on Windows during initial implementation, I encountered some cases where injecting pen input would take a non-trivial amount of time per event and lead to a massive backlog of input events that caused input latency. Unfortunately, it's not always easy to reproduce (perhaps it depends on the window message processing latency of the focused application). We should probably have some batching to ensure we aren't sending pen events at a completely insane rate that the OS can't keep up with.

[Douvahkiin]

@cgutman Is it possible to make it an option? Users can choose whether to have batching or not.