Navigation rewrite: Add WPT for initiator origin in document state

[chromium-wpt-export-bot]

Per one of the remaining work items 1 in the navigation & session history spec rewrite, we need to store the original initiator origin of a given session history entry's document state.

This CL introduces a test to ensure that the initiator origin in a document state is indeed used in history navigations. The way we test this is by:
1.) Producing a session history of [A] -> [B], in order to set [B]'s initiator origin to [A] (also we disable bf-cache). [A] and [B] are cross-site
2.) Navigate back to [A] ([B] is destroyed), and perform location.replace([B])
3.) Then perform history.forward() to initiate a same-origin history navigation to a session history entry whose document state has a cross-origin initiator origin
4.) Confirm that the history.forward() [B] loads with request parameters consistent with the document state that captures state from the original initiator. For example:

• Sec-Fetch-Site: cross-site, implying that the initiator origin was
  saved to the document state and correctly re-used upon subsequent
  navigation (even by a same-origin document).
• Referer: cross-origin, implying that it was correctly written to
  the document state the first time, and reused later
• document.referrer (same as above)

R=[email protected]

Bug: N/A
Change-Id: I2361ef7d5d516e71ad3026626db97a5b9fdb8e38
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3936785
Reviewed-by: Domenic Denicola <[email protected]>
Commit-Queue: Dominic Farolino <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1056900}

[wpt-pr-bot]

The review process for this patch is being conducted in the Chromium project.

[jcscottiii]

ERROR /speculation-rules/prerender/visibility-state.html - Error: assert_implements: <script type="speculationrules"> is not supported undefined looks unrelated. Going to rebase and push again

[WeizhongX]

@jcscottiii, are you working on this? can we admin merge this now?

[WeizhongX]

WPT Command: python3 ./wpt run --channel=nightly --verify --verify-no-chaos-mode --verify-repeat-loop=0 --verify-repeat-restart=10 --github-checks-text-file=/home/test/artifacts/checkrun.md --affected base_head --log-mach-level=info --log-mach=- -y --no-pause --no-restart-on-unexpected --install-fonts --no-headless --verify-log-full --binary=/home/test/build/firefox/firefox firefox

Some affected tests had slow results:

Slow tests

Test	Result	Longest duration (ms)	Timeout (ms)
/html/browsers/browsing-the-web/history-traversal/document-state.tentative.https.html	OK	9795	10000
/performance-timeline/not-restored-reasons/performance-navigation-timing-same-origin-bfcache.window.html	OK	8778	10000

These may be pre-existing or newly slow tests. Slow tests indicate that a test ran very close to the test timeout limit and so may become TIMEOUT-flaky in the future. Consider speeding up the test or breaking it into multiple tests. For help, please tag @web-platform-tests/wpt-core-team in a comment.

[past]

This is a newly added test, so the slowness is likely introduced in this CL. @domfarolino, @domenic maybe you could split it up?

I'll admin merge the PR in the meantime.

[domfarolino]

document-state.tentative.https.html is just a single test, I honestly don't see any way to make it faster, and I can't imagine why it is taking almost 10 seconds to run anywhere.