fix(services): wrap service list responses in an object

[Ysh204]

Summary

This PR addresses the behavior described in tempoxyz/tempo#6576.

services list was the only command returning a top-level JSON array, while similar commands such as keys and sessions list already return top-level objects.

When tempo wallet is used through MCP integrations, clients such as Claude Code reject the top-level array returned by services list. This change wraps service list responses in a top-level object, matching the existing pattern used by other list commands.

Example output:

{
  "services": [
    ...
  ]
}

This also applies to filtered service list responses (for example, --search), ensuring all service list outputs share the same shape.

Changes

• Wrap service list responses in { services: [...] }

• Update the corresponding output schema

• Add regression tests covering:

  • the generated schema
  • CLI JSON output for services

Testing

Test Files  7 passed (7)
Tests       107 passed (107)