Document DEBUG subcommands

[stockholmux]

The docs have a container for the DEBUG command but the subcommands remain undocumented.

There are very useful subcommands here, many of which have been around for a decade without proper documentation. It's obvious that these commands are potentially highly dangerous and blocked by default, but documenting them for normal users has real utility.

As an example, DEBUG POPULATE is super useful to a lot of folks testing out an Valkey, I don't think it's reasonable to keep this information from users.

[madolson]

We didn't document them in Redis since that implies we won't break them in the future without deprecating them. We don't want anyone to take a dependency. We just need to make that behavior clear. I think we should also only selectively document them.

[stockholmux]

I think that's fine @madolson .

I'd welcome any feedback about the safe to document ones.

Alternately, would it make sense to mark the unsafe ones as 'experimental' ?

[stockholmux]

I think this can accomplish by using the output of DEBUG HELP and dumping it to the /commands/debug.md.

Maybe something that does some simple parsing and removing the subcommands that falls outside of "selectively document" criteria.

It would probably also be useful to coverenable-debug-command from conf since that's a gate for DEBUG