Fix stale syncResponse state in overloaded executeQuery

[siyumiG]

If a query takes longer than 5 seconds (the sync query timeout), the driver leaves the statement in a state indicating the query is not done (jobComplete = false) inside the syncResponseFromCurrentQuery reference.

The standard executeQuery(String) method correctly cleans up this state in its finally block. However, the overloaded method executeQuery(String, boolean) used for unlimited billing queries omitted this cleanup.

Consequently, when Looker later calls close() (which invokes cancel()), the driver incorrectly thinks the query is still running and attempts to cancel it. This cancel request fails with a 400 Bad Request (if the query already finished) or a 403 Forbidden (if using restricted OAuth scopes), causing query results to be overwritten by a fatal "Failed to kill query" exception.

This change adds this.syncResponseFromCurrentQuery.set(null); to the finally block of the overloaded executeQuery(String, boolean) method, aligning it with the standard execution path and preventing erroneous cancellation attempts.

Bug: b/522228414, b/523362913

[gemini-code-assist]

Code Review

This pull request updates BQStatement.java to reset syncResponseFromCurrentQuery to null in the finally block of executeQuery to ensure proper state cleanup. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.