Reland "Switch telemetry over to use typ to run the unit tests."

Reland "Switch telemetry over to use typ to run the unit tests."

Original review: https://codereview.chromium.org/659293003

Using typ allows us to run the tests in parallel and share
the logic for parsing the results and uploading them to the
flakiness dashboard with other python test steps.

TBR=dtu@chromium.org, tonyg@chromium.org, nduca@chromium.org, dpranke@chromium.org
BUG=402172, 388256
Committed: https://chromium.googlesource.com/chromium/src/+/fc4a811ffe26653019e2213947146a721620e0fc

[commit-bot: I haz the power, 2014-11-05 14:22:00]

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

[Paweł Hajdan Jr., 2014-11-05 14:22:40]

Committed patchset #1 (id:1) manually as
fc4a811ffe26653019e2213947146a721620e0fc (presubmit successful).

[Paweł Hajdan Jr., 2014-11-05 15:25:24]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/708483002/ by phajdan.jr@chromium.org.

The reason for reverting is: This seems to return with 0 exit code when tests
are failing, see e.g.
http://build.chromium.org/p/chromium.mac/builders/Mac10.9%20Tests%20%28dbg%29...
. Previous build was correctly reporting the steps as failed
(http://build.chromium.org/p/chromium.mac/buildstatus?builder=Mac10.9%20Tests%....

[Dirk Pranke, 2014-11-05 15:40:38]

Hi Paweł,

I appreciate you trying to clean things up, but please do not TBR changes like
this. It's important that the other reviewers and I actually understand what's
going on on the bots and what code is live.

TBR'ing is fine for when the tree is broken and changes need to be reverted, but
this isn't that case and there's no reason for this to land in a hurry.