Add more tentative WPT tests for render-blocking elements

[chromium-wpt-export-bot]

This patch adds more WPT tests for:

• Parser-inserted preload links
• Script-inserted stylesheet and preload links
• Script-inserted style elements

Bug: 1271296
Change-Id: I8f6ffc6a191370410da56b64d7ff8dba852e2732
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3435366
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#967088}

[wpt-pr-bot]

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

[DanielRyanSmith]

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 inconsistent (flaky) results:

Unstable results

Test	Subtest	Results	Messages
/html/dom/render-blocking/render-blocked-apis-by-preload-link.tentative.html	Should not run the scroll steps when render-blocked	FAIL: 2/10, PASS: 8/10	promise_test: Unhandled rejection with value: "'scroll' event is dispatched"

These may be pre-existing or new flakes. Please try to reproduce (see the above WPT command, though some flags may not be needed when running locally) and determine if your change introduced the flake. If you are unable to reproduce the problem, please tag @web-platform-tests/wpt-core-team in a comment for help.

[DanielRyanSmith]

crbug/1294304 created. @past, can you force-merge this PR?

[xiaochengh]

Hmm, this is a newly proposed feature, and I'm not expecting Firefox to pass it.

I'll look into it.

[past]

Merged, thanks!