Bug 1580408 [wpt PR 18987] - [resource-timing] Report performance ent…

…ries with failing status codes, a=testonly

Automatic update from web-platform-tests
[resource-timing] Report performance entries with failing status codes

Currently we don't report performance entries with failing status codes.
From the spec's perspective, reporting aborts is a MAY, but failing
status code responses should not be considered aborts. [1]
Chromium is the only engine which doesn't report those entries.
This CL fixes that to report them similarly to successful status codes.

Bug: 883400, 990849
Change-Id: Ic5e99e3df77f3869aa0dd70f0141d88016fdb972

[1] w3c/resource-timing#165 (comment)

Change-Id: Ic5e99e3df77f3869aa0dd70f0141d88016fdb972
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796544
Commit-Queue: Yoav Weiss <yoavweisschromium.org>
Reviewed-by: Yutaka Hirano <yhiranochromium.org>
Reviewed-by: Mike West <mkwstchromium.org>
Cr-Commit-Position: refs/heads/master{#695596}

--

wpt-commits: 807956fd31824995580dcf36661520452083f9ef
wpt-pr: 18987

UltraBlame original commit: 4505f6c2d2041449bde579b4909491f8e0c97047