Bug 1723199 [wpt PR 29851] - Reporting: Allow document token to change, a=testonly

Bug 1723199 [wpt PR 29851] - Reporting: Allow document token to change, a=testonly

Automatic update from web-platform-tests
Reporting: Allow document token to change

Since the RenderFrameHostImpl is reused for same-origin navigations,
the reporting source token must be able to change when a new document
is loaded into the frame. This is important for reporting isolation when
reports are still queued for the old document.

WPT is added to catch the situation where not changing this token would
cause previously queued reports to be sent to the new document's
configured endpoints.

This is part of a series of CLs implementing V1 reporting isolation.
A summary of the architectural changes introduced can be found at
https://docs.google.com/document/d/1RmEz17pGSUQITPoRKV4s3IBgbyHjv-HLZqtVYYZ4lMg/edit

CLs in this series:
https://crrev.com/c/2878175 Update NEL browser tests to require Report-To
https://crrev.com/c/2878376 Separate parsing from processing Reporting-Endpoints
https://crrev.com/c/2889833 Add reporting source to worker objects
https://crrev.com/c/2889975 Add reporting source to COOP/COEP reporters
https://crrev.com/c/3039579 Add source token to reports
https://crrev.com/c/3041880 Add source token to IPC calls
https://crrev.com/c/3042463 Isolate v1 reports from each other
https://crrev.com/c/3042465 (This CL) Allow document source token to change
https://crrev.com/c/3042521 Clean up when docs/workers are destroyed

Bug: 1062359
Change-Id: I908e49b7b773c57335f8c527843643c896082ce4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3042465
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Lily Chen <chlily@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/main@{#914491}

--

wpt-commits: b5c4ae1193387f99dc2bd7e723ed8561e56a137f
wpt-pr: 29851