server: the "range" status API endpoint should work with secondary tenants with sufficient capability #110018
Description
Found while investigating #110001.
Describe the problem
When TestRangeResponse in server/storage_api is modified to point to a secondary tenant (e.g. via #110008), the test starts failing when accessing the /_status/range (NB: not ranges) endpoint:
ranges_test.go:153: got the wrong number of ranges in the response, expected 1, actual 0
How to reproduce
from #110008 reset DefaultTestTenant, run the test with a test tenant and observe the failure.
Expected behavior
Once the tenant is granted a suitable capability, the endpoint should work properly.
Epic CRDB-38968
Jira issue: CRDB-31224