perf: Swap CROSS JOIN table ordering back to previous version

[tkaemming]

Problem

This may be the cause for recent problematic memory increases on EU cluster as noted as a possibility in #27890.

Changes

Reverts back to the slower but more memory optimized version.

Does this work well for both Cloud and self-hosted?

Yes.

How did you test this code?

Snapshots, et cetera

[greptile-apps]

PR Summary

This PR reverts a previous optimization in the query execution order to address memory usage concerns in the EU cluster, specifically affecting CROSS JOIN operations in trend analysis queries.

• Reverts table ordering in _actors_inner_select_query method to prioritize memory efficiency over speed
• Change primarily impacts queries using 'monthly_active' math operations which require storing 16-byte UUIDs for distinct count aggregations
• Trades off ~10x performance improvement for lower memory consumption, particularly important for memory-constrained environments
• Addresses potential memory issues reported in EU cluster while maintaining functionality across both cloud and self-hosted deployments

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}