Make double tap simulation less picky about multitouch reporting details

It should no longer matter whether SYN_MT_REPORT is used by the touch
driver or not - or what kind of subset of PRESSURE, TOUCH_MAJOR and
TRACKING_ID multitouch events are used for the touch point reporting.

[mce] Make double tap simulation less picky about multitouch reporting details. Fixes JB#19916
Merge pull request #174 from spiiroin/doubletap_detection

Make double tap simulation less picky about multitouch reporting details