[event-input] Expose touch and volume key policy on D-Bus. JB#38001

Originally the mechanism used for stopping touch screen and volume key
events from reaching ui layers was to disable the hw generating them.
As this is not always possible, mce was modified so that it grabs evdev
input device nodes instead. That too is problematic in devices that use
multitouch protocol B and/or emit volume key events from input devices
that can't be grabbed for some reason (such as providing also power key).

As an enabler for UI side event filtering, expose the mce side input
policy decisions on dbus. When the relevant UI components listen to
these signals and handle/ignore input events accordingly, there is no
need for mce to grab any input device nodes anymore.

Also change the activation/deactivation of the opt-in debug led pattern
PatternTouchInputBlocked to be based on the policy decision rather than
grabbing/ungrabbing of touch input device nodes.

Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

.depend

@@ -69,6 +69,7 @@ event-input.o:\
 	evdev.h\
 	event-input.h\
 	mce-conf.h\
+	mce-dbus.h\
 	mce-io.h\
 	mce-lib.h\
 	mce-log.h\
@@ -84,6 +85,7 @@ event-input.pic.o:\
 	evdev.h\
 	event-input.h\
 	mce-conf.h\
+	mce-dbus.h\
 	mce-io.h\
 	mce-lib.h\
 	mce-log.h\