Add tests to account for resource-timing/fetch integration changes

[noamr]

During the integration of FETCH/ResourceTiming, some subtle changes were made.
WPT needs to account for them.

• fetchStart and startTime when TAO-protected should not expose redirect time
• transferSize is always encodedBodySize + 300 or 0 (if cached). It shouldn't expose actual cookie value.
• nextHopProtocol should be TAO protected: https://github.com/web-platform-tests/wpt/blob/master/resource-timing/nextHopProtocol-is-tao-protected.https.html
• Once the different initiator definition is done, the tests need to account for the details (see Create resource timing entries for HTML resources whatwg/html#6542)
• It's unclear whether service-workers/cached responses should carry forward some of the connection info. (When response comes from a worker, some of the timing-info should pass through whatwg/fetch#1208) - tests exists, see https://wpt.live/service-workers/service-worker/resource-timing-fetch-variants.https.html
• Once we reach consensus on network errors, add tests to account for specified behavior (Clarify which network errors create a resource timing entry whatwg/fetch#1215)

[noamr]

@yoavweiss

[yoavweiss]

Would it make sense for this issue to sit in the resource timing repo?

[noamr]

Would it make sense for this issue to sit in the resource timing repo?

I don’t have a clear opinion on this... whatever is customary

[yoavweiss]

The transferSize parts were covered as part of https://chromium-review.googlesource.com/c/chromium/src/+/2878693