Set CONFIGURATION_NAME to be used in base.isolate.

Set CONFIGURATION_NAME to be used in base.isolate.

Enables precise control of the isolate depending on correct
versions of msvc*.dll.

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

[scheib, 2014-07-08 00:18:59]

I've tested on windows with:
1. ninja -C out\Release browser_tests_run
2. python tools\swarming_client\isolate.py run -s
out\Release\browser_tests.isolated

I haven't tested build/android/pylib/gtest/setup.py -- unsure if there is
reasonable try job coverage of that or if I should manually test it -- let me
know.

[M-A Ruel, 2014-07-08 11:52:58]

On 2014/07/08 00:18:59, scheib wrote:
> I've tested on windows with:
> 1. ninja -C out\Release browser_tests_run
> 2. python tools\swarming_client\isolate.py run -s
> out\Release\browser_tests.isolated
> 
> I haven't tested build/android/pylib/gtest/setup.py -- unsure if there is
> reasonable try job coverage of that or if I should manually test it -- let me
> know.

It's fine, isolate files are actively being used by the android tester in try
jobs, so you'll get coverage.

lgtm, thanks!

[M-A Ruel, 2014-07-08 11:53:14]

The CQ bit was checked by maruel@chromium.org

[commit-bot: I haz the power, 2014-07-08 11:53:49]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/scheib@chromium.org/373973002/1

[commit-bot: I haz the power, 2014-07-08 12:46:17]

Change committed as 281730