Key unfinished resources by GlobalRequestId in ads page load metrics

Move the resource map to use GlobalRequestID instead of the blink
request id to avoid any case of renderers having ongoing requests with
conflicting id's. These resources are aggregated across renderers and
blink request ids are only unique per-renderer.

It is not expected this will have a noticeable difference in histograms.
Request ids start at a random number in each renderer from 0->2^20,
are then incremented by one for each request. We only care about collisions
for two ongoing resource loads which is expected to be somewhat rare. Thus
the associated Ads.ResourceUsage.* metrics and PageLoad.Clients.Ads.Bytes
histograms will not be versioned.

Bug: 943598
Change-Id: I9e599856a043d38d029cec6665e0a38776f2c3ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1529661
Commit-Queue: John Delaney <johnidel@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#642192}
23 files changed