basalt-26.3: sql/row: TestRowFetcherMemoryLimits failed [OOM]

sql/row.TestRowFetcherMemoryLimits [failed](https://mesolite.cluster.engflow.com/invocations/default/d239d62a-5965-4976-9f91-d90c819f20c9?testReportRun=1&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvc3FsL3Jvdzpyb3dfdGVzdA==) on basalt-26.3 @ [017b84cd0101b832a6ee0c1934d073d108d0b24a](https://github.com/cockroachdb/cockroach/commits/017b84cd0101b832a6ee0c1934d073d108d0b24a):

```
=== RUN TestRowFetcherMemoryLimits
test_log_scope.go:172: test logs captured to: outputs.zip/logTestRowFetcherMemoryLimits3111939134
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=1
- shard=1
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:.*TestRowFetcherMemoryLimits.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-68056

Start with sql/row.TestRowFetcherMemoryLimits and the linked test report for commit 017b84cd0101b832a6ee0c1934d073d108d0b24a. Review the captured logs under outputs.zip/logTestRowFetcherMemoryLimits3111939134 and the test_server_shim.go context, using the race, run, shard, and attempt parameters. Done means the cause of the OOM is identified and the test passes under the reported configuration.

Written by the indexing model from the issue text.