Remove forced static_library build for Dr. Memory now that the tool

Remove forced static_library build for Dr. Memory now that the tool
supports the debug MSVS libc dll.  Also disabled debug build inlining
and FPO to support increasing debug build optimization.

Re-add unit_tests to the "Windows Tests (DrMemory)" bot.  (The
unit_tests cannot be linked with static_library, which is why they
were removed from the bot.)

BUG=137180
R=rnk@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=151770

[Reid Kleckner (google), 2012-08-15 21:10:17]

LGTM

I assume you're going to submit https://chromiumcodereview.appspot.com/10823349/
first, after its try job finishes.  Otherwise the m.fyi drmemory bot will
flicker red.

We'll also need a separate change to the bot configs to start running unit_tests
again, and after that a master restart.  :(  This just controls what targets are
built.

[Derek Bruening, 2012-08-15 21:28:13]

On 2012/08/15 21:10:17, Reid Kleckner (google) wrote:
> > I assume you're going to submit
https://chromiumcodereview.appspot.com/10823349/
> first, after its try job finishes.  Otherwise the m.fyi drmemory bot will
> flicker red.

yes that is the plan