Query results incorrectly assigned expired status by Looker API

[joshtemple]

Looker's async multi_results endpoint occasionally reports the status of a running query as expired right before the query completes successfully. This causes spectacles to incorrectly mark the query as errored, when in fact, the query was successful.

In a previous change, we considered marking all expired queries as complete, but this becomes a problem if a query is killed manually (see report in #104) since it's subsequently marked as expired.

We will reach out to Looker to see if we can reproduce and fix the expired issue.

[iserko]

Just had it happen on our instance:

Attempting to get results for 1 query tasks
Query task a607517addb9d3159300ee61d314e40e status is running
Attempting to get results for 1 query tasks
Query task a607517addb9d3159300ee61d314e40e status is expired
Attempting to get results for 1 query tasks
Query task a607517addb9d3159300ee61d314e40e status is error

[joshtemple]

Checking in on this issue to confirm that this is still a problem in 2023. I'm seeing log patterns that look exactly like what iserko posted above, where a query goes from expired to error status.