Currently when a user generates a query that contains an aggregation we move them to the aggregations page. However, if the AI model also returns a query bar field, like a sort (which might also exist in the aggregation), we will keep them on the query page. This likely results in some folks reporting negative feedback that nothing was generated. Instead, when an aggregation is returned with at least one stage, we should redirect them to the aggregations page and disregard the query.

After deploying this we should try to see if the results are what we expect. If we find that oftentimes it moves folks to the aggregation tab when the query tab would have been fine, we likely don't want these changes, and we should revert.