Fix initial datapipe state assumptions

Use defaults that are least likely to cause state machines to wake up
during device bootup or mce restart.
Use constants instead of hard coding exception durations
Improve handling of external display/tklock state changes

Try to get in sync when exception state changes, i.e. even though call
ui handling was out of sync, a freshly started notification might not.

Any tklock changes during exception causes the display and tklock
state not to be restored after exception ends, i.e. if ui side is
unlocked during notification or call, the display is not blanked
afterwards.

Also the exception data pipe contains only the currently active bit
instead of the whole bitmask.
Touch input activity makes notification exceptions last longer

In practice this allows user more time to interact with dialogs
related with device lock, audio routing etc
Probe initial state for jack_sense_pipe too
Allow module / function specific debug logging

Just setting mce to debug mode generates so much noise it is no
longer useful for debugging. After the changes for example

  mce -T -l'tklock.c:*datapipe_*' -l'tklock.c:*except*'

can be utilized to get debug logging only from datapipe changes
seen by tklock module and the exception state machine activity
resulting from them.
Block late suspend during notification exception

This allows UI side to process the event too even if we can't turn on
the display due to for example proximity sensor.
Activate power on pattern when ACT_DEAD -> USER transition starts

The old behavior was to toggle it on/off during power key press, which
was confusing because the pattern is so similar to charging pattern.

Also remove legacy deactivation code that is either not triggered
at all or comes too early.
Activate led pattern if frame buffer suspend/resume takes too long

After the change we should be able to tell apart display blank/unblank
problems that are caused by 1) mce 2) kernel 3) stuck ui
Make adaptive dimming threshold longer

Basically this needs to be at least as long as the DIM->BLANK delay.

As that blank timeout was made longer, the adaptive dimming gets
disabled couple of seconds before the screen is blanked.