[Telemetry] Increase timeout for HasBrowserFinishedLaunching

[Telemetry] Increase timeout for HasBrowserFinishedLaunching

Empirically it can take chrome up to 40 seconds to come up for a cold start on the 10.6 bots. Increase the timeout in Telemetry to reduce test flakiness.

BUG=405386
Committed: https://crrev.com/6ed88af6fd662b3c1fbbaa16d36aeaf13f4a37d6
Cr-Commit-Position: refs/heads/master@{#295248}

[jeremy, 2014-09-17 07:30:49]

jeremy@chromium.org changed reviewers:
+ marja@chromium.org, nednguyen@google.com

[jeremy, 2014-09-17 07:30:50]

Ned/Marja: Owner review please, whoever gets to this first...

[marja, 2014-09-17 07:36:00]

lgtm;

Routing some not-really-offline discussion here: it's a bit surprising (to me)
that it takes 40 s for the browser to start, but jeremy@ says it's as expected
on the bot (e.g., on old hardware).

[jeremy, 2014-09-17 07:37:46]

The CQ bit was checked by jeremy@chromium.org

[commit-bot: I haz the power, 2014-09-17 07:39:01]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patchset/568673004/1

[commit-bot: I haz the power, 2014-09-17 09:05:05]

Committed patchset #1 (id:1) as 0f4a1101dfd1d3e935068edb06ba6782921479a3

[commit-bot: I haz the power, 2014-09-17 09:05:44]

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