Check how blink requests are prioritized

[uazo]

with the 124, chromium sends via http header the priority of the request (note: the information was already present in the http3 frames, but is now made available at the application level).

from https://chromestatus.com/feature/5109106573049856/activity:

This feature indicates the priority of a resource as determined by certain heuristics in Chrome. As these resources might be included in a cross-site context, the feature has the potential of revealing information based on these heuristics.

check:

• https://web.dev/articles/fetch-priority#browser-priority-and-fetchpriority
• ResourceFetcher::ComputeLoadPriority and ResourceLoadPriority enum