Query tabs have unexpected behavior

__Proposal:__
In cloud 2.0 UI, if you create two queries in two tabs, I would have expected the behavior to be that if I clicked 'submit' while the first tab is active, the first query would be executed and its results shown in the data explorer, and if I clicked 'submit' while the second tab is active, the second query would be executed and its results shown in the data explorer.

__Current behavior:__
Currently, the results of all queries are displayed simultaneously in the data explorer.

__Desired behavior:__
Queries can be run independently.

__Alternatives considered:__
Remove the tabs if we can only support running all queries in parallel, or change the UI in some way to make it clearer that all the queries are executing (I don't have any good ideas for what this UI might look like).

__Use case:__
Why is this important (helps with prioritizing requests)? User confusion, as it's not consistent with other tabbed experiences.

Start by reproducing the behavior in the Cloud 2.0 UI with two query tabs, then inspect how Submit sends queries and displays results in the data explorer. Done means the active tab's query runs independently and its results are shown without automatically displaying the other tab's results.

Written by the indexing model from the issue text.