debug: make it easy to retrieve range IDs for a corresponding table/index/partition from debug zips

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

Pre-coalesced ranges, one could figure out what ranges contain a given table's data using something like:

```
۩ rg "/Table/17070" -l | grep '.json'
debug/nodes/5/ranges/54143.json
debug/nodes/13/ranges/52065.json
debug/nodes/1/ranges/52067.json
debug/nodes/3/ranges/54143.json
debug/nodes/3/ranges/52065.json
debug/nodes/3/ranges/52067.json
debug/nodes/10/ranges/52065.json
debug/nodes/2/ranges/52067.json
debug/nodes/7/ranges/52065.json
debug/nodes/7/ranges/54143.json
debug/nodes/7/ranges/52067.json
```

That's not reliable now that we don't split on schema boundaries by default. We still include the binary form of start/end keys in the individual nodes//ranges/.json files:

```
"range_id": 33,
"start_key": "rQ==",
"end_key": "rg==",
```

But to go from these keys to the specific table/index ID of interest (the data might sit somewhere just within a range) is cumbersome.

**Describe the solution you'd like**

We could make this easier, perhaps by including output for all `SHOW RANGES FOR WITH DETAILS` in our debug zip.

Jira issue: CRDB-30319