server/application_api: TestAdminAPIDatabaseDetails failed

server/application_api.TestAdminAPIDatabaseDetails [failed](https://mesolite.cluster.engflow.com/invocations/default/5bfb4faf-02ac-4445-8fa2-1f163941e06f?testReportRun=3&testReportShard=8&testReportAttempt=1#targets-Ly9wa2cvc2VydmVyL2FwcGxpY2F0aW9uX2FwaTphcHBsaWNhdGlvbl9hcGlfdGVzdA==) on master @ [5318641d2b0ff04dbdaced9f83ecb0d692f697b6](https://github.com/cockroachdb/cockroach/commits/5318641d2b0ff04dbdaced9f83ecb0d692f697b6):

```
=== RUN TestAdminAPIDatabaseDetails
test_log_scope.go:172: test logs captured to: outputs.zip/logTestAdminAPIDatabaseDetails6741399
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.
test_server_shim.go:637: DRPC is enabled (via testserver factory defaults)
schema_inspection_test.go:469:
Error Trace: pkg/server/application_api/schema_inspection_test.go:469
pkg/testutils/soon.go:76
pkg/util/retry/retry.go:393
pkg/testutils/soon.go:82
pkg/testutils/soon.go:59
pkg/testutils/soon.go:38
pkg/server/application_api/schema_inspection_test.go:456
Error: "0" is not positive
Test: TestAdminAPIDatabaseDetails
Messages: ApproximateDiskBytes
schema_inspection_test.go:473: -- test log scope end --
test logs left over in: outputs.zip/logTestAdminAPIDatabaseDetails6741399
--- FAIL: TestAdminAPIDatabaseDetails (116.13s)
```

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

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

/cc @cockroachlabs/obs-prs

[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-68155

Start with TestAdminAPIDatabaseDetails in pkg/server/application_api/schema_inspection_test.go, especially the retry around lines 456-473, and reproduce the failure using the linked test report and commit. Inspect the captured logs for why ApproximateDiskBytes remains 0; done means the test passes with a positive value.

Written by the indexing model from the issue text.