New test for Chrome M32 optimisation

M32 removes double-tap-to-zoom (which does nothing?) on
width=device-width only pages (w/out need for extra user-scalable=no and
similar)
typo duh!
expand pointer detect page

list actual number of reported touch points (and then test if, say,
nokia lumia 520 correctly identifies as 5)
touch/click delay test with touch-action:none
tweak to touch-action:none click delay page
Variation of particle field just with pointermove
particle field w/pointermove and touch-action:none
Tweaks to particle field demos and isPrimary check
add new demos to index
particle field - mouse only

added original demo without any touch support, shifted all other demos
by one letter
modified index for particle field demos
added touchcancel to list of identified events
navigator.pointerEnabled is deprecated

replace test with window.PointerEvent
removed redundant hover test

covered already by mouse-only test
changed event order that's added

Safari/iOS7 seems to only fire mouseenter/mouseleave when no touch event
listeners have been registered? Seeing if changing the order in which
they're added makes any difference, or if it's some sort of Safari
heuristic (if touch events registered, ignore mouseenter/mouseleave part
of the compatibility mouse events)
quick test for iOS/Safari

in testing so far, Safari/iOS7 has not fired any events when tapping
away from "Test button!". wondering if this only happens when tapping to
some other activatable element instead...another heuristic?
iOS test split out to separate page

so we keep the clean "all events, no timings" demo
filename typo