Figure out cold start issue with chromedriver performance logs

Problem/Motivation

In ✨ Add OpenTelemetry Application Performance Monitoring to core performance tests Fixed I discovered that the very first request that chromedriver makes in a test with the performance log enabled only appears to create entries for the 'network' log (http requests etc.), not the 'performance' log (which includes things like first contentful paint and largest contentful paint candidates).

It's easy to workaround, but it's also a gotcha if you don't realise this, so it would be good to track down firstly if other people get the same problem, and if so, probably post an upstream bug report.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet