Longshot feature idea: integrate CrUX API?

[Chrome provides an API ](https://developer.chrome.com/docs/crux/api/)to query their "CrUX" data (Chrome Rel user experience data). This data shows the CWV scores for real logged in Chrome users.

I'm currently using this API to diagnose some slow FID times on a client site. But, I've got to do everything by hand which is tricky when there are lots of URLs. It could be cool if you could optionally query the CrUX API for CWV scores for all of the URLs on your site. This could be another data point to include in spreadsheets and histograms.

One advantage of this data source is that it's real user data: it's not influenced by the machine hitting the API and represents real user experiences. It can also test for metrics like FID which can't be measured without a real user.

I'm not sure it it makes sense to integrate this into Lighthouse Parade. It may be a longshot. But the idea occurred to me so I thought I'd throw it out there and see what folks think.

Start with the linked Chrome CrUX API documentation and review how Lighthouse Parade currently gathers data for crawled URLs and presents spreadsheets or histograms. No implementation files or tests are named; done would require an agreed scope for optional CrUX queries and their resulting data.

Written by the indexing model from the issue text.