issue-489: ported chromium windows decommitting code

I tried to do it cleanly with merges but chromium code has so many
relevant commits (with frequent reverts) that makes it near
impossible.

Simpler 2-way emerge-files worked in the end. I've removed chromium's
aggressive 'always decommit' behavior which I want to make optional
later.

Majority of this work is the following commits (but there are more,
particularly against port.cc):

commit 9c92338c5f8770c440799d24387c3733fd6d826b
Author: jamesr@chromium.org <jamesr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date:   Tue Oct 6 18:33:31 2009 +0000

    Tracks the amount of committed vs uncommitted memory in tcmalloc's page heap's freelists

    Keeps track of the number of reserved but not committed pages in the freelist and uses that to calculate a waste metric, which is the ratio of committed pages vs pages used by the application.  This is exposed in the GetStats() call (which is used for about:tcmalloc) and through GetNumericalProperty() in Malloc

    BUG=none
    TEST=open about:tcmalloc and monitor 'WASTE' columns while using the browser

    Review URL: http://codereview.chromium.org/251065

    git-svn-id: svn://svn.chromium.org/chrome/trunk/src@28133 0039d316-1c4b-4281-b951-d872f2087c98

commit aef4f1be3eec2059a7c6e2c106050a5f3d6ccf12
Author: jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date:   Mon Oct 5 17:58:51 2009 +0000

    Revert further back to MBelshe's baseline forking TCMalloc

    This changes to decommitting in all paths through the
    page_heap delete method (which adds spans to the free lists).

    r=mbelshe,jamesr
    Review URL: http://codereview.chromium.org/255067

    git-svn-id: svn://svn.chromium.org/chrome/trunk/src@28006 0039d316-1c4b-4281-b951-d872f2087c98

commit e94afbb913b95f512cb8745a2729c73f82b15ae7
Author: jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date:   Thu Oct 1 00:25:41 2009 +0000

    Rollback Scavenge implemetation and rely on existing functionality to free

    This is a landing of a patch provided by antonm.  See:
    http://codereview.chromium.org/235022

    Also included change to browser_about_handler.cc to fix build, and I set
    TCMALLOC_RELEASE_RATE to 1.0 on line 40 of page_heap.cc (I think this
    was an inadvertent rollback element).

    r=antonm
    Review URL: http://codereview.chromium.org/257009

    git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27692 0039d316-1c4b-4281-b951-d872f2087c98

commit c585892d2c42a47c95d06a684a6685156c545403
Author: mbelshe@google.com <mbelshe@google.com@0039d316-1c4b-4281-b951-d872f2087c98>
Date:   Wed Sep 2 17:33:23 2009 +0000

    Landing for Anton Muhin's tcmalloc patch:
    http://codereview.chromium.org/180021/show

    Restore decommitting in IncrementalScavenge and draft Scavenge method to
    be invoked periodically
    to reduce amount of committed pages.

    BUG=none
    TEST=none

    Review URL: http://codereview.chromium.org/187008

    git-svn-id: svn://svn.chromium.org/chrome/trunk/src@25188 0039d316-1c4b-4281-b951-d872f2087c98

commit 14239acc00731e94736ac62e80fc6b17c31ea131
Author: mbelshe@google.com <mbelshe@google.com@0039d316-1c4b-4281-b951-d872f2087c98>
Date:   Wed Aug 12 02:17:14 2009 +0000

    Major changes to the Chrome allocator.

    Changes include:
    * Fix tcmalloc to release memory.  Implements the TCMalloc_SystemCommit()
      mechanism so that tcmalloc can implement SystemRelease() and later
      reuse that memory.
    * Enable dynamic switching of allocators based on an environment variable.
      Users can now switch between tcmalloc, jemalloc, the default windows
      heap, and the windows low-fragmentation heap.
    * Implements set_new_mode() across all allocators so that we can be sure
      that out-of-memory conditions are handled safely.

    BUG=18345
    TEST=none; plan to get all unit tests running through these allocators.

    Review URL: http://codereview.chromium.org/165275

    git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23140 0039d316-1c4b-4281-b951-d872f2087c98
issue-489: fixed warning

Computing certain values just for ASSERT raises just warning from
compiler because if NDEBUG is set those are dead code.
issue-489: made DecommitSpan handle failed SystemRelease

Chromium "agressive decommit" code is a user of DecommitSpan
method. And compared to chromium code, our's SystemRelease may
fail. It makes sense to propagate this failure and handle stats
accordingly.
issue-489: implemented API to set chromium-style de-committing

Chrome has code to decommit (release back to OS) every span that's
released. I don't want to make it default, but indeed some
applications may want to enable this mode.

The code itself is taken from 2-way-merging of code from Chromium
fork.