Revert of Precisely determine Windows thread stack size.

Revert of Precisely determine Windows thread stack size. (patchset #2 id:20001 of https://codereview.chromium.org/1409243011/ )

Reason for revert:
This apparently caused HeapTest.TraceDeepEagerly to crash on all Win bots (here's an example build: http://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win%20x64%20Builder/builds/65297)

Original issue's description:
> Precisely determine Windows thread stack size.
>
> The Thread Information Block (TIB)'s StackLimit records the end of
> the committed area of the thread's stack reservation, hence it cannot be
> used to determine the overall size of the reserved stack. Switch to
> a VirtualQuery() lookup instead, but taking care to cache the result per
> thread so as to avoid calling overhead.
>
> R=haraken
> BUG=546396
>
> Committed: https://crrev.com/7a23dd77ae2fd895fac2b4dcd8a542f575b6d1ac
> Cr-Commit-Position: refs/heads/master@{#356287}

TBR=oilpan-reviews@chromium.org,sigbjornf@opera.com
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=546396
Committed: https://crrev.com/36b8f5dcd71cb2af3d131ce68cd9141a52bed896
Cr-Commit-Position: refs/heads/master@{#356321}

[caseq, 2015-10-27 17:03:41]

Created Revert of Precisely determine Windows thread stack size.

[haraken, 2015-10-27 17:04:55]

LGTM

[commit-bot: I haz the power, 2015-10-27 17:05:05]

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

[commit-bot: I haz the power, 2015-10-27 17:07:08]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-10-27 17:09:06]

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