fix(enterprise): services get/status fails for cm_server despite services list succeeding

[joshrotenberg]

Summary

redisctl enterprise services list works against the local Enterprise demo cluster, but targeted get and status calls for cm_server fail.

Reproduction

Against the local demo stack on https://localhost:9443:

redisctl enterprise services list --profile local-enterprise
redisctl enterprise services get cm_server --profile local-enterprise
redisctl enterprise services status cm_server --profile local-enterprise

Observed result:

• services list succeeds
• services get cm_server fails
• services status cm_server fails

Expected behavior

If cm_server is a valid service name surfaced by services list, the targeted commands should either:

• succeed for that same name, or
• reject it with a clear explanation of the supported identifier format

Why this matters

This smells like a mismatch between the identifier surfaced by list and the identifier expected by get / status, which makes the command set internally inconsistent.

Acceptance criteria

• Reproduce against the local Enterprise demo stack
• Determine whether list is surfacing the wrong identifier or get/status are expecting the wrong one
• Align the commands so names returned by list are actually usable in targeted calls, or document/translate identifiers explicitly

Context

Found during live Enterprise integration testing.