fix: return error when custom getQueryResults() timeout has been exceeded

[steffnay]

It is currently possible to set options.timeoutMs when calling Job.getQueryResults(). The timeoutMs value is how long to wait for the query to complete, in milliseconds, before the request times out and returns. If the timeout is exceeded before the query completes, the API returns a response that includes jobComplete: false. However, due to the way that auto-pagination is handled, the client still continues to make getQueryResults() requests until the query completes.

This change updates Job.getQueryResults() to return an error when a custom timeout has been exceeded, rather than continuing to check for query results.

Job.createQueryJob() is also updated to allow job.configuration.jobTimeoutMs to be set.

Fixes #823 🦕

[codecov]

Codecov Report

Merging #872 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #872   +/-   ##
=======================================
  Coverage   98.65%   98.65%           
=======================================
  Files           9        9           
  Lines        6967     6986   +19     
  Branches      418      422    +4     
=======================================
+ Hits         6873     6892   +19     
  Misses         94       94           

Impacted Files	Coverage Δ
src/bigquery.ts	99.95% <100.00%> (+<0.01%)	⬆️
src/job.ts	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update be7c6e6...fd0b5ff. Read the comment docs.