Include actuated state into active_keys

[girlglock]

Now that we can get the actuated state from the interface it would be useful to also include it into active_keys

0 for not actuated, 1 for actuated and null/undefined for when its not supported (it might need a more clever type for easier handling)

however there is still a bit of work to be done that i didnt yet figure out... we need a way to differentiate from it being available via analog interface v2 or not since turning off rapid trigger via wootility will make packed & 0x1 result in either 0 or 1 unrelated to the actuation (im assuming that its being used for something else with rt off)

[Sainan]

I mean, this information is certainly interesting, but it's Wooting-only so the already-existing APIs for gleaming digital keyboard input are going to be more useful regardless.

[girlglock]

my thought process for this was: "why coordinate two different apis if we can have two birds with one stone"
it might be worth adding even if not vastly supported (assuming the rt issue can be resolved)