Explore: Results for at least one previous Prometheus data source rendered when changing data source to a tracing source

### What happened? When querying a data source (in this case any Prometheus data source) that returns results, if the user changes the data source to use to any tracing data source (currently tested with Tempo, Jaeger and X-Ray), the results from the Prometheus query are still rendered in the newly changed data source query editor. The issue is not consistent, but happens for the majority of queries (and does appear to be instant-query based as requring a prior table of results). Example uses Grafana SE demo kit, employees can see [the video here](https://drive.google.com/file/d/1m2xdy9DxxWg50tarxYZBg0fOAYTl2RR4/view?usp=drive_link) for a demonstration of the problem. ### What did you expect to happen? The newly selected trace data source should not show the results from the previous Prometheus query. ### Did this work before? 11.1.0 ### How do we reproduce it? 1. Go to [`sedemo`](https://sedemo.grafana.net/explore), select any Prometheus data source (see video). 2. Write a valid PromQL query that returns instant results. 3. Switch to a tracing data source. 4. Observe previous results rendered in tracing data source results table. This doesn't *always* happen, but it is frequent (>50% of queries tested). ### Is the bug inside a dashboard panel? _No response_ ### Environment (with versions)? Grafana: Grafana v11.3.0-74868 (4a753dd2d5) OS: N/A Browser: Firefox (https://www.whatsmybrowser.org/b/1K3IO) also Chrome (https://www.whatsmybrowser.org/b/HM3UP). Appears to be browser agnostic. ### Grafana platform? I use Grafana Cloud ### Datasource(s)? Prometheus, Tempo, X-Ray, Jaeger, Zipkin...