fix pointer types detection placement

Currently, we're getting false-negatives on touch-action tests in browsers that only support touch-action (e.g. Chrome) because the pointerType property is being used by the logic that updates the informational notice of what pointer types are used. Since this notice is just a useful affordance for the tester, this shouldn't impact test results.

This PR moves the informational notice's logic out of critical test logic code paths to avoid these false-negatives. It also ensures all the tests have this affordance.