We might unset focus, or already be out of focus (e.g. an X11 client or clutter text entry is focused) when a text-input state is committed by the client. We handled this before, except when text input was explicitly disabled by the client, the Wayland text-input was in focus by the input method, and it focused itself out.
Simplify the logic a bit by just dropping the state on the floor in all cases where after any potential focus changes were done, we are not focused.
Fixes: #353 (closed)