[BUG] Control topic `host.stop.<id>` needs empty payload

[lachieh]

Affected project(s)

• [ ] documentation
• [ ] examples
• [X] wasmCloud host
• [ ] wasmCloud CLI (wash)
• [ ] wasmCloud dashboard UI (washboard)
• [ ] capability providers
• [ ] provider bindgen
• [ ] control interface client
• [ ] other / not sure

Describe the bug

Not really a bug per se but it'd probably be nice to adjust this behavior.

The host.stop.<id> topic for the control api requires an empty payload to work, but it doesn't really need one.

Steps to reproduce

➜ nats request "wasmbus.ctl.v1.default.host.stop.NAJPHEQ347GXSFPJXOW7YOINDT6L33HEORKSY2E6CWSHQUTQJRCGKHP2" "" --raw | jq
{
  "success": false,
  "message": "failed to deserialize stop command"
}

➜ nats request "wasmbus.ctl.v1.default.host.stop.NAJPHEQ347GXSFPJXOW7YOINDT6L33HEORKSY2E6CWSHQUTQJRCGKHP2" "{}" --raw | jq
{
  "success": true,
  "message": ""
}

Expected behavior

The first example above would ideally pass

Environment

wasmCloud 1.0

Screenshots / Logs / Additional context

No response