core(runner): fix missing timing properties in the browser

[exterkamp]

Summary
PerformanceEntries in Lightrider (and the extension) had no names and no entryTypes. This manifested as a 0 timing.total in the API as well.

@brendankenny found that browser PerformanceEntry objects do not spread, but in Node they do b/c of the marky lib. So, simple fix to explicitly call out the name and entryType fields when parsing the entries. This will also populate the missing lh:runner:run entry to fill in timing.total.

Related Issues/PRs
fixes: #8638

[brendankenny]

@brendankenny found that browser PerformanceEntry objects do not spread, but in Node they do b/c of the marky lib

marky makes its own PerformanceEntry objects, which spread just fine, but the properties on a native PerformanceEntry are getters in the prototype chain, so nothing is spread.

Interestingly, running LH in DevTools seems to defeat marky's environment sniffing and so it uses the fallback objects and the entries are ok. The extension is like lr here and only has {startTime, duration}

[patrickhulce]

bam nice work! with 1.5 quarters to spare too 😎

[connorjclark]

can we add a hexa test to LR