chore: cache error tracking query longer

[daibhin]

Problem

Error tracking queries are not being cached for long enough

Changes

Without the query_date_range the cache_target_age interval gets set to minute, which results in a 15 second cache. Bumping the interval to hour will cache for 15 minutes which feels more reasonable for the error tracking query

[neilkakkar]

something to eventually think about: One workflow I love with sentry is:

1. I go into a user account to try and repro a bug. This throws an error
2. I immediately go into sentry to find the issues in the last few minutes to correlate and find the right one (maybe some searches as well, but it can sometimes be hard to figure out what to search for, like in async cohort recalculation celery tasks)
3. Sentry shows me the exact issue and I can go from there

With caching for 15 minutes at a time, this workflow becomes much more painful...

[daibhin]

I think what we can do here for the case Neil mentioned is to use the cached results if present but continue to load in the background to refresh the cache. I believe this is called lazy_async but will need to confirm with the product analytics folks. And for how to implement that within the data table logic... 🤷‍♂️

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week. If you want to permanentely keep it open, use the waiting label.

[posthog-bot]

This PR was closed due to lack of activity. Feel free to reopen if it's still relevant.