Always copy touch event's LatencyInfo into gesture event's LatencyInfo

Previously we only copy touch event's LatencyInfo into gesture event's
LatencyInfo when the touch event does not cause any rendering. This is
based on the assumption that if the touch event causes any rendering,
it should be consumed so no gesture event is actually generated.
This could be wrong that touch event is not prevented default, but it
still causes rendering and turns into gesture event.

So the simple solution is we always copy some of the touch event's
LatencyInfo that we are interested in into gesture event's LatencyInfo,
regardless of whether the touch event causes rendering or not.

BUG=338819
TEST=Follow the test in the bug and make sure the first GestureScrollUpdate
     contains the some key latency components from the TouchMove's LatencyInfo.

Review URL: https://codereview.chromium.org/146303004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@249749 0039d316-1c4b-4281-b951-d872f2087c98
Use validating form of IPC enum macros for frame messages.

This is part of a long-running background task to remove the remaining
uses of the unchecked IPC_ENUM_TRAITS() macro.

BUG=246708

Review URL: https://codereview.chromium.org/143003023

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@249750 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 249750