Epic: Improve Service Provider Developer Experience

[maximiliantech]

Goal

Extend OpenMCP documentation to improve developer experience for Service Provider and Cluster Provider contributors.

Problem Statement

Contributors building providers face several documentation gaps that create a steep learning curve:

• Cluster architecture unclear: Developers don't know which cluster (platform, onboarding, MCP, workload) to use and which clients to use where
• Namespace patterns undocumented: Tenant namespaces, platform namespaces, installation namespaces are not clearly explained
• Testing/debugging challenging: E2E testing pitfalls and debugging in multi-cluster setups are not documented
• Local development friction: Manual kubeconfig patching required for local development

Context

This epic focuses on improving existing documentation for Service Provider and Cluster Provider development. Platform Service documentation is covered separately by #514.

Q2 Acceptance Criteria

See sub-issues below

Out of Scope

• Platform Service documentation (covered by Epic: Enable PlatformService contributions #514)
• ProviderConfig documentation (covered by Epic: Document deprecated ProviderConfig handling  #517)
• Operator and end-user documentation (owned by other SIGs)
• Development environment setup overhaul (Development environment setup needs some love docs#34 — SIG Core scope)
• Renaming to OpenControlPlane (owned by SIG Core)

Stakeholders

• @Skarlso — original feedback on documentation gaps
• @christophrj — contributor working on several issues
• SIG Extensibility — ownership of developer documentation