feat: add plugin for deploying Camunda 8 to a local kind cluster

Problem

c8ctl already unifies two of our three documented Self-Managed local deployment options:

• c8run — via the built-in cluster default plugin
• docker-compose — via the c8ctl-plugin-dev plugin

The third documented option, kind, has no c8ctl plugin. Users who want to test the Helm chart path locally have to fall back to the manual kind create cluster + helm install steps from the docs, outside the c8ctl tooling.

Proposal

Add a kind plugin (either a new default plugin alongside cluster, or a standalone c8ctl-plugin-kind following the c8ctl-plugin-dev model) that:

• Creates/deletes a local kind cluster pre-configured for Camunda 8 (ingress, port mappings, etc. per the docs guide)
• Installs the camunda-platform Helm chart against it with sane local-dev defaults
• Exposes start/stop/status commands consistent with cluster start/stop semantics
• Reuses camunda-platform-helm chart values rather than duplicating config

Value

Would give us one CLI (c8ctl) to stand up all documented Self-Managed local options (c8run, docker-compose, kind), instead of splitting kind/Helm testing into a separate manual workflow.

References

• c8run plugin: default-plugins/cluster in this repo
• docker-compose plugin: https://github.com/camunda/c8ctl-plugin-dev
• kind deployment docs: https://docs.camunda.io/docs/next/self-managed/deployment/helm/cloud-providers/kind/

Start with the kind deployment guide and the existing default-plugins/cluster implementation; compare its start, stop, and status semantics with the proposed kind workflow. Review c8ctl-plugin-dev for the standalone plugin model. Done means a kind-based plugin can create and remove the configured cluster, install the Camunda Helm chart with local defaults, and expose consistent lifecycle commands.