[DevTools Bug]: Can’t import chrome trace into react devtools

### Website or app https://tsk9sq.csb.app/ ### Repro steps 1. Go to the page and open devtools 2. Go to performance tab and start recording 3. Interact with the application 4. Stop recording 5. Download trace 6. Upload to react devtools 7. Expected - React timeline tab should display trace 8. Actual - React devtools fails to import the trace and shows an error - "e.sort is not a function. Try importing another Chrome performance profile."  I think its is an issue with how we are parsing the chrome trace [here](https://github.com/facebook/react/blob/e3ebcd54b98a4f8f5a9f7e63982fa75578b648ed/packages/react-devtools-timeline/src/import-worker/importFile.js#L22C1-L23C1). Chrome outputs the trace file in the following format: ```json { "traceEvents": [ {"name": "Asub", "cat": "PERF", "ph": "B", "pid": 22630, "tid": 22630, "ts": 829}, {"name": "Asub", "cat": "PERF", "ph": "E", "pid": 22630, "tid": 22630, "ts": 833} ], "displayTimeUnit": "ns", "systemTraceEvents": "SystemTraceData", "otherData": { "version": "My Application v1.0" }, "stackFrames": {...} "samples": [...], } ``` but react devtools expects the file to contain only `traceEvents` array. React DevTools should be able to handle both formats because they are valid according to this document: https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview ### How often does this bug happen? Every time ### DevTools package (automated) _No response_ ### DevTools version (automated) _No response_ ### Error message (automated) _No response_ ### Error call stack (automated) _No response_ ### Error component stack (automated) _No response_ ### GitHub query string (automated) _No response_