haptic: Use event configuration based haptic event type detection

The ffmemless plugin was using effect configuration based *_TOUCH key
to detect if effect is touch interaction related to filter it out
in case touch haptics is disabled from profile. This got broken when
the can_handle policy was moved to haptic.c. And also it was never
working for android vibrator plugin.

Fixed the touch haptic detection by replacing the ffmemless specific
key with a event configuration based "haptic.type" key that will apply
right policy to all vibra plugins utilizing n_haptic_can_handle function.

The haptic.key currently supports type strings "alarm" and "touch". This
may be appended in the future if there is some need.

Currently default policy does not block haptic playback if "haptic.type"
key is missing for event, but it may be used for that in the future to
for example move the call state handling from haptic.c to event
configuration files, like it's done for audio now.

Signed-off-by: Kalle Jokiniemi <kalle.jokiniemi@jolla.com>
Yes, the %s is a good idea, though it's actually not mandatory to have the haptic.type, if the event does not want to have haptic effects.. hence maybe this should not be a warning but a N_DEBUG with the %s giving the event. Sound OK?