Further instrumentations to find jank in Windows message processing.

Further instrumentations to find jank in Windows message processing.
Based on the latest revelations:
440919 WindowImpl::WndProc2 = 90 jph.
Since the internals of OnWndProc are instrumented, this strangely indicates that it's GetWindowUserData who is responsible for this jank. Instrumenting it.

440919 <<MessagePumpForUI::ProcessNextWindowsMessage>> = 46 jph and
440919 MessagePumpForUI::ProcessMessageHelper = 39 jph
This means that with instrumenting MessagePumpForUI::ProcessMessageHelper, we've divided MessagePumpForUI::ProcessNextWindowsMessage into 2 roughly equal parts: everything that happens inside MessagePumpForUI::ProcessMessageHelper, and everything outside (GetQueueStatus and PeekMessage).
Adding in instrumentation to separate GetQueueStatus from PeekMessage.
Also instrumenting internals of MessagePumpForUI::ProcessMessageHelper.

BUG=440919
Committed: https://crrev.com/4949a513d841da01d66a32f54a98fec518c3fde3
Cr-Commit-Position: refs/heads/master@{#310156}

[vadimt, 2015-01-05 21:54:29]

vadimt@chromium.org changed reviewers:
+ cpu@chromium.org

[vadimt, 2015-01-05 21:54:29]

cpu@, please review

[cpu_(ooo_6.6-7.5), 2015-01-06 20:46:13]

lgtm

https://codereview.chromium.org/835183002/diff/1/ui/gfx/win/hwnd_util.cc
File ui/gfx/win/hwnd_util.cc (right):

https://codereview.chromium.org/835183002/diff/1/ui/gfx/win/hwnd_util.cc#newc...
ui/gfx/win/hwnd_util.cc:124: return NULL;
It would be very surprising if this is a bottleneck. I am betting is not.

[vadimt, 2015-01-06 20:47:36]

The CQ bit was checked by vadimt@chromium.org

[commit-bot: I haz the power, 2015-01-06 20:48:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/835183002/1

[commit-bot: I haz the power, 2015-01-06 22:08:09]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-01-06 22:09:01]

Patchset 1 (id:??) landed as
https://crrev.com/4949a513d841da01d66a32f54a98fec518c3fde3
Cr-Commit-Position: refs/heads/master@{#310156}

[falken, 2015-01-07 02:50:35]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/830423008/ by falken@chromium.org.

The reason for reverting is: Speculative revert for Windows failures on Blink
waterfall. They also appear on the trybots so will try a tryjob first..