Reimplementation of touch screen and keypad locking subsystem

Legacy automatic locking is replaced with two state machines. One
deals with time based delayed locking after display off and another
one that deals with proximity based locking after display off.

Exceptional ui states - where the display is turned on to handle
things like calls, alarms and notifications - have a state machine of
their own. Each exception type can also utilize display on linger,
i.e. the display can be kept on a while after the exceptional state
has already ended.

The keypad, touchscreen and doubletap event enable / disable logic for
legacy devices is also implemented as a single state machine. The
basic logic was smoketested on a old nemomobile image with N9 and N950
devices, but there might still be rough edges at corners.

The two separate ON -> DIM -> OFF engines in tklock and display
modules have been joined to a single engine at display module.

Mere activity is no longer used to unblank the display. This requires
explicit display on request. The power key and double tap handling has
been modified to handle this.

The pocket mode is removed. It needs to be re-implemented when/if low
power mode display can be supported again.

The N9 specific display on statistics gathering was removed as it
requires Nokia specific libcal and we are unlikely to have that
available in nemomobile.

The late suspend is delayed for one second after reaching display off
state. This should give UI side time to handle display off actions
before suspend rather than after resume.

If setUpdatesEnabled D-Bus method calls take unexpectedly long time, a
led pattern is activated. This should allow us to tell apart black
screens that result from ui / dbus freeze from other causes.

[mce] Reimplementation of touch screen and keypad locking subsystem
Disable unit test building

The unit test modules are out of sync with implementation and
can't be compiled for now.
Remove unmaintained modules/displaymeego.[ch]

It has not been actively maintained and does not work with the
new tklock implementation.
Separate wakelock name and timeout with space when writing to sysfs

While the space was missing caused permanent wakelock instead of a
one that would be automatically cancelled.
Use mce_abort() instead of plain abort()

So that autosuspend gets disabled and wakelocks released before
mce terminates.
Add human readable submode change diagnostic output
Tune logging levels

Make things less noisy by default.

Use mce specific LL_xxx levels instead of syslog LOG_xxx ones.
Add LL_ALERT logging level

For use as easy to find development time alias for LL_NOTICE.
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.
Restore power on led deactivation at desktop startup notification

Turns out that was the correct trigger for normal bootup.
Tune debug logging for power on led toggling