Track state of connections and devices in higher-level request/event helpers

[ids1024]

Though the implementation here seems to work (and reis-demo-server passes the upstream test suite), we should have equivalents of libei's enum eis_seat_state, enum ei_seat_state , enum eis_device_state , enum ei_device_state, enum eis_client_state, and enum ei_state.

[glamberson]

I've been working on EIS integration in a couple different Wayland compositor projects and ran into the gap this issue describes: reis works correctly at the wire level, but consumers end up reimplementing state tracking that libei handles internally.

I've submitted PR #21 with ConnectionState, SeatState, and DeviceState enums covering the equivalents of eis_client_state/ei_state, eis_seat_state/ei_seat_state, and eis_device_state/ei_device_state. Each wrapper tracks its own state as protocol events flow through. I also included pressed key/button/touch tracking since libei ties that to the pause/resume lifecycle.

While working on this I also found a couple of related protocol correctness gaps, so I submitted PR #22 (cleaning up interfaces on destroy) and have a third PR ready for Release request handling. Happy to adjust any of these based on feedback.

Thanks,

Greg Lambeson
Lamco Development
greg@lamco.io
https://lamco.ai