Handle timedelta in query results

[wlach]

What type of PR is this?

• Refactor
• Feature
• Bug Fix
• New Query Runner (Data Source)
• New Alert Destination
• Other

Description

(this is a follow-on to #6837)

Since #6687, we don't serialize query results as JSON before returning them. This is fine, except for the
query results data source which needs to pass the data directly to sqlite3, and doesn't know how to
do that with the timedelta types that are occasionally returned by (at least) the PostgreSQL query runner:

https://www.psycopg.org/docs/faq.html#problems-with-type-conversions

How is this tested?

• Unit tests (pytest, jest)
• E2E Tests (Cypress)
• Manually
• N/A

Related Tickets & Documents

N/A

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

[wlach]

@justinclift @eradman Another one to look at when you have a sec

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.50%. Comparing base (38a06c7) to head (bbad55e).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #6846   +/-   ##
=======================================
  Coverage   63.50%   63.50%           
=======================================
  Files         163      163           
  Lines       13206    13209    +3     
  Branches     1824     1825    +1     
=======================================
+ Hits         8386     8389    +3     
  Misses       4518     4518           
  Partials      302      302           

Files	Coverage Δ
redash/query_runner/query_results.py	63.23% <100.00%> (+0.82%)	⬆️

[justinclift]

@eradman Are you ok to look over this one?

Looking over it, it seems super simple. 😁

[eradman]

This looks good; effectively the same as casting to text in the query.