## Is your feature request related to a problem?

If you have a trend with multiple lines, clickhouse queries for each are run one-after-another. If each takes 10s to calculate, then user will need to wait >30s in total.

## Describe the solution you'd like

Run queries in parallel.

## Describe alternatives you've considered

## Additional context

cc @EDsCODE @neilkakkar This seems like a quick win query-api wise though not 100% sure on how best implement this. Would you be up for prioritizing this _next_ sprint?

#### *Thank you* for your feature request – we love each and every one!

ee/clickhouse/queries/trends/clickhouse_trends.py
serialized_data = []
        serialized: Dict[str, Any] = {
            "action": entity.to_dict(),
            "label": entity.name,
            "count": 0,
            "data": [],
            "labels": [],
            "days": [],
        }
        for queried_metric in result:
            serialized_copy = copy.deepcopy(serialized)
            serialized_copy.update(queried_metric)
            serialized_data.append(serialized_copy)
        return serialized_data
    def _handle_cumulative(self, entity_metrics: List) -> List[Dict[str, Any]]:
        for metrics in entity_metrics:
            metrics.update(data=list(accumulate(metrics["data"])))
        return entity_metrics