i have an input pin in my case. i'm just designing an API where i get a `PinState` and have to check `is_low` / `is_high` to check if it's the desired state - if i'd have a `state` in e-h (which would do that internally) then i could just compare against that, making my user code cleaner.
i'm just thinking "i can't be the only one to want that" so i'm wondering if i should create a PR to add it (since it'd have an impl in e-h it'd have no impact on HALs and would be non-breaking).

a similar thing is also for e-h-a: besides a `wait_for_low` and `wait_for_high` it'd be nice to have a `wait_for_state` (which again would just intern `match` on the state and call one or the other).

just some nice convenience abstractions