Input batching

[cgutman]

Description

Certain input events, like pen/mouse, can be generated so frequently that we cannot inject them as fast as we receive them. This leads to significant latency accumulating as we get further and further behind, until we finally catch up when the client stops sending more input.

This PR implements input batching for these input types (controller state/touch/motion, pen/touch, mouse motion) to avoid this issue. Moonlight performs similar batching on the client side.

Screenshot

Issues Fixed or Closed

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

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated