release-26.4: testutils/testcluster: TestClusterSqlDisabled failed

testutils/testcluster.TestClusterSqlDisabled failed on release-26.4 @ b4884d371d74d172ab184bc4ef0924ccb758f3c2:

=== RUN   TestClusterSqlDisabled
    test_log_scope.go:172: test logs captured to: outputs.zip/logTestClusterSqlDisabled3716475825
    test_log_scope.go:82: use -show-logs to present logs inline
    testcluster_test.go:65: -- test log scope end --
test logs left over in: outputs.zip/logTestClusterSqlDisabled3716475825
--- FAIL: TestClusterSqlDisabled (1612.91s)
=== RUN   TestClusterSqlDisabled/disable-sql=false
--- FAIL: TestClusterSqlDisabled/disable-sql=false (1274.96s)
=== RUN   TestClusterSqlDisabled/disable-sql=false/test-tenant={1_true_false_0_}
    testcluster.go:665: polling for queued jobs to complete: poll-show-jobs: session record deleted
--- FAIL: TestClusterSqlDisabled/disable-sql=false/test-tenant={1_true_false_0_} (1076.48s)

Parameters:

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

Jira issue: CRDB-68560

Start with testutils/testcluster.TestClusterSqlDisabled and the failure at testcluster.go:665. Run the test with the linked logs or -show-logs, then compare the polling path for the disable-sql=false tenant case. Done means the test no longer fails with “session record deleted” on the affected release branch.