Update blanking inhibit also during frame buffer suspend/resume

The dim/blank timers are programmed after stable display state is
reached, but the inhibit flags must me evaluated also during the
transitional states.

[mce] Update blanking inhibit also during frame buffer suspend/resume
Block display ON/DIM D-Bus requests during call/alarm/proximity

Powering on display when we have active call or alarms could interfere
with the built-in rules for handling those situations.

And if proximity is covered, the display should turn on only via
power key press.

[mce] Block display ON/DIM D-Bus requests during call/alarm/proximity
Fix whitespace
Keep proximity sensor always enabled

Disabling proximity sensor during display DIM meant it was re-enabled
via sensord just before suspending, without guarantees that it actually
gets enabled before the device suspends.

It is still possible to use run time configuration to disable the
proximity sensor.

[mce] Keep proximity sensor always enabled
Do not turn display on after call ends

MCE has no way of knowing what has happened at UI side during the
call. Whether the display is on or off after the call ends should
be left for lipstick to decide.

[mce] Do not turn display on after call ends
Merge pull request #107 from spiiroin/dbus_display_on

Block display ON/DIM D-Bus requests during call/alarm/proximity