There's a more fundamental question about structure here too.
The documentation is not a arbitrary block of text. It contains
specific data items for individual parameters, and return
type, along with version number annotation too.
If we're returning a single string, then the caller needs to
know how to parser the current docs structure we're using
for commands. Right now that's an internal only format, and
I'm not sure we want to expose that as an ABI to consumers
of QEMU. So quite possibly we need to return structured
data instead
eg potentially we need
{ 'struct': 'CommandDocumentation',
'data': {'name': 'str',
'summary': 'str'
'description: 'str'
'parameters': ['str'],
'return': str,
'since': str,
'notes': str,
'example':str,
} }