release-26.2: sql/tests: TestSplitAtTableBoundary failed [OOM]

sql/tests.TestSplitAtTableBoundary [failed](https://mesolite.cluster.engflow.com/invocations/default/0b28285c-61a6-4609-8a34-ad9511645e62?testReportRun=2&testReportShard=16&testReportAttempt=1#targets-Ly9wa2cvc3FsL3Rlc3RzOnRlc3RzX3Rlc3Q=) on release-26.2 @ [af7b3170ea0bf609c97954e8db045e95ee3c430b](https://github.com/cockroachdb/cockroach/commits/af7b3170ea0bf609c97954e8db045e95ee3c430b):

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

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

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

Same failure on other branches

- #174750 sql/tests: TestSplitAtTableBoundary failed [C-test-failure O-robot T-sql-queries branch-master release-blocker]
- #174697 basalt-26.3: sql/tests: TestSplitAtTableBoundary failed [C-test-failure O-robot T-sql-queries branch-basalt-26.3 release-blocker]

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

Jira issue: CRDB-68010

Start with the linked TestSplitAtTableBoundary failure report and captured outputs.zip logs, then read the test_server_shim.go comment because the report notes an injected shared process virtual cluster. Compare the same failure reports on master and basalt-26.3. Done means identifying the OOM cause, making the appropriate test or infrastructure change, and confirming the test passes under the reported race configuration.

Written by the indexing model from the issue text.