Introspection query trace not available after it fails

### Expected Behavior

1. Set up a GQL query using Bearer Auth -- and verify the query works OK
2. Expect Insomnia to be able to fetch the schema
3. OR if Insomnia is unable to fetch the schema, expect that I can examine the trace/timeline of the introspection query to investigate why it failed

### Actual Behavior

1. The introspection query fails with a 400
2. The trace/timeline for the introspection query is unavailable

Per https://github.com/Kong/insomnia/pull/970 I would expect to be able to investigate the timeline for the query (to figure out why it's 400'ing in my case, despite the actual query working fine), but I don't see any way to do so:

### Reproduction Steps

1. Set up a GQL query using Bearer Auth
2. Either have automatic schema fetch enabled or manually fetch the schema

### Is there an existing issue for this?

- [X] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.

### Additional Information

I have a hunch for why this might be 400'ing on our GQL server, but without access to the query log for the introspection query, I'm having a hard time proving it. Other coworkers have seen the same behavior with Insomnia.

### Insomnia Version

2022.7.0

### What operating system are you using?

macOS

### Operating System Version

macOS Monterey 12.5.1

### Installation method

download from insomnia.rest

### Last Known Working Insomnia version

_No response_

Start by reproducing the failed GraphQL introspection query with Bearer Auth and inspect how Insomnia records request traces and timelines. The issue is complete when a failed introspection request exposes its trace or timeline so the 400 response can be investigated.

Written by the indexing model from the issue text.