Refactoring timing info for ServiceWorker controlled requests [1/3]

Refactoring timing info for ServiceWorker controlled requests [1/3]

Currently, three timings are collected for ServiceWorker controlled
requests: serviceWorkerFetchStart, serviceWorkerFetchReady, and
serviceWorkerFetchEnd. However serviceWorkerFetchReady and
serviceWorkerFetchEnd are always the same value as sendStart and
sendEnd, respectively.

This three sided patch removes serviceWorkerFetchReady and
serviceWorkerFetchEnd, and renames serviceWorkerFetchStart to
workerStart, which is the name used in Navigation Timing and Resource
Timing.

[1/3] THIS
[2/3] https://codereview.chromium.org/1157823003/
[3/3] https://codereview.chromium.org/1151263003/

BUG=465640
TEST=no functional change; all existing tests should pass.

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=195894

[Kunihiko Sakamoto, 2015-05-26 01:11:03]

Patchset #1 (id:1) has been deleted

[Kunihiko Sakamoto, 2015-05-26 01:47:55]

ksakamoto@chromium.org changed reviewers:
+ horo@chromium.org, pfeldman@chromium.org

[Kunihiko Sakamoto, 2015-05-26 01:47:56]

PTAL

[horo, 2015-05-26 05:21:08]

lgtm

[pfeldman, 2015-05-26 05:55:08]

lgtm

[Kunihiko Sakamoto, 2015-05-26 06:10:17]

The CQ bit was checked by ksakamoto@chromium.org

[commit-bot: I haz the power, 2015-05-26 06:10:36]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1159663002/20001

[commit-bot: I haz the power, 2015-05-26 07:08:25]

Committed patchset #1 (id:20001) as
https://src.chromium.org/viewvc/blink?view=rev&revision=195894