Is your feature request related to a problem? Please describe.

PR #79546 introduces crdb_internal.probe_range, but it won't be available during troubleshooting sessions unless included in a debug.zip.

Describe the solution you'd like

Include a query such as

SELECT count(1) FROM crdb_internal.probe_ranges(INTERVAL ‘1000ms’, ‘write’) WHERE error != '' ORDER BY end_to_end_latency DESC LIMIT 100;

(the LIMIT gives a very approximately ~1000ms*100 target on how long this can
take, so that running debug.zip against an unavailable cluster won't take too
long)

Describe alternatives you've considered

Additional context

Jira issue: CRDB-15754