basalt-26.3.2-rc-20260908: ccl/serverccl: TestExecSQL failed

ccl/serverccl.TestExecSQL failed on basalt-26.3.2-rc-20260908 @ 807558e5e81666af257c811e925e4cae570abc28:

=== RUN   TestExecSQL
    test_log_scope.go:172: test logs captured to: outputs.zip/logTestExecSQL496628396
    test_log_scope.go:82: use -show-logs to present logs inline
    panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestExecSQL496628396
--- FAIL: TestExecSQL (70.06s)
=== RUN   TestExecSQL/sql_drop_table
    datadriven.go:263: 
          testdata/api_v2_sql:473:
          sql admin
          {
            "database": "mydb",
            "execute": true,
            "statements": [
              {"sql": "DROP TABLE bar"}
            ]
          }
        output didn't match expected:
          @@ -1,6 +1,17 @@
           {
          + "error": {
          +  "code": "XXUUU",
          +  "hint": "The job may not have succeeded.",
          +  "message": "operation \"run-sql-via-api\" timed out after 5.019s (given timeout 5s): job 1211579745433092097 could not be loaded: txn exec: context deadline exceeded",
          +  "severity": "ERROR",
          +  "source": {
          +   "file": "txn.go",
          +   "function": "exec",
          +   "line": 1188
          +  }
          + },
            "execution": {
             "txn_results": [
              {
               "columns": [
                {
--- FAIL: TestExecSQL/sql_drop_table (5.06s)

Parameters:

• attempt=1
• race=true
• run=1
• shard=1

Start with ccl/serverccl.TestExecSQL, especially the sql_drop_table case and testdata/api_v2_sql:473. Inspect the captured test logs from outputs.zip/logTestExecSQL496628396 and rerun the test with -show-logs. Done means the operation no longer times out and the expected output matches.