fix(hidpp10): validate Receiver register and event parsers

[jelmerdehen]

Summary

Several Receiver methods index device-supplied response buffers and HID++ reports without checking the buffer length:

• getNotificationFlags, getConnectionState, getDeviceActivity, getPairingInfo, and getExtendedPairingInfo dereference bytes from a register response that the device controls.
• deviceConnectionEvent, fillDeviceDiscoveryEvent, pairStatusEvent, boltPairStatusEvent, discoveryStatusEvent, and passkeyEvent only assert on subId / type and then index paramBegin()[N]. Asserts compile out under NDEBUG, so a malicious or buggy device can feed a Short report to a Long-expecting parser and trigger out-of-bounds reads up to ~14 bytes past the heap allocation.

logid runs as root, so reads here are at minimum an information leak from a process the device should not be able to read.

Fix

• Replace assert with runtime checks that throw std::runtime_error on bad subId / type.
• Validate response and paramEnd - paramBegin length before indexing.

Throwing was chosen over silent return so the calling state machine sees the error and can drop the malformed report instead of acting on uninitialized fields.

Test plan

• Builds cleanly.
• Pair / unpair flows on Bolt and Unifying receivers still work.
• Stub a Short response to a Long-expecting parser and confirm we throw rather than read OOB.