basalt-26.3: sql/physicalplan: TestFakeSpanResolver failed

sql/physicalplan.TestFakeSpanResolver [failed](https://mesolite.cluster.engflow.com/invocations/default/376fcf97-274a-4e7c-ad0a-4aafab7d24f7?testReportRun=2&testReportShard=3&testReportAttempt=1#targets-Ly9wa2cvc3FsL3BoeXNpY2FscGxhbjpwaHlzaWNhbHBsYW5fdGVzdA==) on basalt-26.3 @ [c6d01ae4be9708178b248a49819b505daf713377](https://github.com/cockroachdb/cockroach/commits/c6d01ae4be9708178b248a49819b505daf713377):

```
=== RUN TestFakeSpanResolver
test_log_scope.go:172: test logs captured to: outputs.zip/logTestFakeSpanResolver2265855593
test_log_scope.go:82: use -show-logs to present logs inline
test_server_shim.go:168: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
```

Parameters:
- attempt=1
- race=true
- run=2
- shard=3
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestFakeSpanResolver.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-68100

Start with sql/physicalplan.TestFakeSpanResolver and reproduce it with the race setting described in the report. Inspect the captured logs at outputs.zip/logTestFakeSpanResolver2265855593 and the test-server behavior documented in test_server_shim.go. Done means the failure is understood and the test passes reliably.

Written by the indexing model from the issue text.