fix: cli reference format in MCP server configuration page

[pratik-naik003]

What this PR does

Fixes the CLI reference code block in docs/source/mcp-server/configuration.rst to match the format used in the upstream MCP server README.

Before (inline comments on each flag)

kubeflow-mcp serve \
  --clients trainer \             # modules: trainer, optimizer (stub), hub (stub)
  --persona ml-engineer \         # readonly | data-scientist | ml-engineer | platform-admin
  --mode full \                   # full | progressive | semantic

After (descriptive comment block above the command)

# Modules: trainer, optimizer (stub), hub (stub)
# Persona: readonly | data-scientist | ml-engineer | platform-admin
# Mode: full | progressive | semantic
...
kubeflow-mcp serve \
  --clients trainer \
  --persona ml-engineer \
  --mode full \
  ...

Why

The website and the README should present the CLI reference consistently. The inline-comment format made lines unnecessarily long and differed from the upstream source of truth.

Fixes #773

[google-oss-prow]

@pratik-naik003: The label(s) kind/documentation cannot be applied, because the repository doesn't have them.

Details

In response to this:

What this PR does

Fixes the CLI reference code block in docs/source/mcp-server/configuration.rst to match the format used in the upstream MCP server README.

Before (inline comments on each flag)

kubeflow-mcp serve \
 --clients trainer \             # modules: trainer, optimizer (stub), hub (stub)
 --persona ml-engineer \         # readonly | data-scientist | ml-engineer | platform-admin
 --mode full \                   # full | progressive | semantic

After (descriptive comment block above the command)

# Modules: trainer, optimizer (stub), hub (stub)
# Persona: readonly | data-scientist | ml-engineer | platform-admin
# Mode: full | progressive | semantic
...
kubeflow-mcp serve \
 --clients trainer \
 --persona ml-engineer \
 --mode full \
 ...

Why

The website and the README should present the CLI reference consistently. The inline-comment format made lines unnecessarily long and differed from the upstream source of truth.

Fixes #773

/kind documentation

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign andreyvelich for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jaiakash]

I dont think this would be need. Both format are fine.

/close

[google-oss-prow]

@jaiakash: Closed this PR.

Details

In response to this:

I dont think this would be need. Both format are fine.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.