cli/debug: include debug=3 goroutine profile in zip

[dt]

Our debug=3 profiles are inteded to be a "best of both worlds" profile that captures the individual goroutine stacks as debug=2 does, while using the minimial stop-the-world pause of debug=0/1 profiles and also including labels (like debug=1) and wait durations (like debug=2).

In the future this might/should be the only profile we ask the production nodes to collect and export: it has a superset of the information of the other two profiles, making it sufficient either for direct analysis or for post-processing into other/textual formats, while also having minimial collection impact on the running nodes. For now however, it is introduced side-by-side with the existing profiles to allow for testing and validation before making it the sole goroutine profile collected.

Release note: none. Epic: none.

[cockroach-teamcity]

This change is 

[dt]

(just the second commit; first is landing in #159253)

[dt]

TFTR!

bors r+

[craig[bot]]

Build succeeded:

• check_generated_code
• linux_amd64_build
• acceptance
• linux_amd64_fips_build
• lint
• examples_orms
• unit_tests
• docker_image_amd64
• local_roachtest_fips
• local_roachtest

[blathers-crl[bot]]

Encountered an error creating backports. Some common things that can go wrong:

1. The backport branch might have already existed.
2. There was a merge conflict.
3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.

---

error creating backport branch refs/heads/blathers/backport-release-26.1-159260: POST https://api.github.com/repos/dt/cockroach/git/refs: 403 Resource not accessible by integration []

Backport to branch 26.1.x failed. See errors above.

---

_{:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[dt]

blathers backport 26.1