core(gather-runner): detect Chrome interstitials

[patrickhulce]

Summary
All part of the plan (#8865 (comment)).

All Chrome interstitials put the user onto chrome-error://chromewebdata which is then all data URLs under the hood. We check the documentURL portion to see if they ended on the chrome error page, if they did and we had a failed request, we fail with a special cased error.

Related Issues/PRs
#8865 (comment)

[benschwarz]

Is this something you could filter devtools logs for the appearance of Page.interstitialShown?

[patrickhulce]

Yeah @benschwarz the more direct way IMO would be using Page.frameRequestedNavigation and finding the reason there. I'm definitely not opposed to doing that but this seemed to align better with our existing model for what counts as a "page load error".

[brendankenny]

yay, this is great. I also like how it has an obvious place for this to live now, so there's one place to detect and handle more interstitial special cases in the future (like if we do ever want to handle t using protocol events instead, or whatever)

[brendankenny]

LGTM!