Fix logic on high Windows resolution timer and have two possible period values for timeBeginPeriod …

Fix logic on high Windows resolution timer and have two possible period values for timeBeginPeriod and timeEndPeriod.

(merging to branch)

Currently while on battery we disable calls to timeBeginPeriod
which make the windows timers have 15ms resolution.

This change makes it so when EnableHighResolutionTimer(true) which
is on AC power the timer is 1ms and EnableHighResolutionTimer(false)
is 4ms.

This should provide significant power savings while meeting some
timer resolution requirements needed by the GPU compositor.

But also this CL fixes the following:

EnableHighResolutionTimer() and ActivateHighResolutionTimer() are
pretty broken. This CL fixes most issues:

1- The existing logic fails to account that EnableHighResolutionTimer
can be called while the browser is running

2- All related functions need to be thread safe.

3- ActivateHighResolutionTimer was buggy.

BUG=153139
Review URL: https://codereview.chromium.org/489793003

Cr-Commit-Position: refs/heads/master@{#292094}
(cherry picked from commit be8f40e67f300e9452cfabb3ad594d907cfaa947)

Committed: https://chromium.googlesource.com/chromium/src/+/08b216ce0ab5e000d2425e472ee009dbb9c7d79a

[cpu_(ooo_6.6-7.5), 2014-09-16 01:30:54]

Committed patchset #1 (id:1) manually as 08b216c.