release-23.1: cli: default --include-range-info to true, but create a single file

[tbg]

Backport 5/5 commits from #104133.

/cc @cockroachdb/release

Release justification: debug.zip improvement that avoids loss of observability after a recent change, and improves UX

---

This was introduced and defaulted to false in
#102289.

Anecdotally I look at these in many L2 escalations¹, and one cannot always
even change the default flag (e.g. CC), and seldom will a later debug.zip be
good enough for an RCA.

The original reason to introduce this flag seems to have been the delay
incurred when extracting these many files. There are suspicions that this
somehow exacerbates broken archives that we get from time to time, esp.
on large clusters.

This PR defaults the flag to true but also switches debug.zip so that it now
puts the ranges into a single file. This file is going to be large, but we can
handle that.

Epic: none
Release note: None

Footnotes

1. most recently today: https://github.com/cockroachlabs/support/issues/2343#issuecomment-1569677115 ↩

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Patches should only be created for serious issues or test-only changes.
• Patches should not break backwards-compatibility.
• Patches should change as little code as possible.
• Patches should not change on-disk formats or node communication protocols.
• Patches should not add new functionality.
• Patches must not add, edit, or otherwise modify cluster versions; or add version gates.

If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

• What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
• Will this work in a cluster of mixed patch versions? Did we test that?
• If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

[cockroach-teamcity]

This change is