feat(mcp): forward tools/call progress to Host

[wutongyuonce]

Summary

Long-running MCP tools currently look frozen: the SDK already supports onprogress / notifications/progress, and Runtime Host already forwards admitted (current, total) as transcript tool_progress, but McpClientManager.callTool never asked for a progress token and the CLI capability provider never called options.progress.

This PR wires those two existing seams. Invalid or incomplete progress is dropped so a noisy server cannot fail the tool. Listeners that throw are ignored for the same reason.

Fixes #5069

Verification

• npm --workspace @maka/mcp run build && npm --workspace @maka/mcp run test:dist — 191 passed
• node --test packages/cli/dist/__tests__/runtime-host-capability-provider-command.test.js — 6 passed
• Did not run root lint / format:check / full npm test

Did not attach UI evidence: this is protocol-to-Host wiring; coverage is the modern Streamable HTTP fixture plus the CLI provider snapshot test.

Review

Independent Codex review (read-only) found no must-fix issues. Follow-up from that review: the omit-onProgress path now asserts the tools/call request has no progressToken. Skipped an extra E2E for invalid payloads — tool-progress.test.ts already covers drop behavior.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: Pi implemented the wiring, tests, issue, and PR text. Codex ran a read-only review.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No