chore(query): Add more timing measures

[timgl]

Problem

Add some more instrumentation so we know where things are slow

Changes

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

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

How did you test this code?

[greptile-apps]

PR Summary

This PR adds comprehensive timing instrumentation to better track performance metrics in HogQL query execution. Here's a focused summary of the key changes:

• Added timing measurements in create_hogql_database for critical operations like session table setup, data warehouse operations, and joins
• Enhanced execute_hogql_query to propagate timing context through HogQLContext and database creation
• Wrapped key database initialization sections in timings.measure() for granular performance tracking
• Added instrumentation for group type mapping and channel/domain type creation
• Improved timing visibility for data warehouse operations including saved queries and table setup

The changes are purely observability-focused and don't modify any core logic, making this a low-risk improvement for debugging performance issues.

_{💡 (2/5) Greptile learns from your feedback when you react with 👍/👎!}

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