[Feature] Native Cloudflare Tunnel integration for domain publishing

What problem will this feature address?

Currently, setting up Cloudflare Tunnel with Dokploy requires manual
steps: deploying cloudflared separately, configuring Traefik, managing
DNS records by hand. Many users struggle with this:

• #966 — Users asking how to set up CF Tunnel with Dokploy
• #2153 — 502 errors after hours of manual setup attempts
• #3472 — Mixed content issues due to incorrect tunnel configuration

Describe the solution you'd like

Cloudflare integration with three runtime modes:

1. Use Existing Tunnel Instance
Routes new domains through an already-running tunnel via CF API.
No new containers needed.

2. Dokploy Managed Shared Connector
Dokploy deploys and manages a single shared cloudflared container.
Multiple domains share one connector.

3. Start Cloudflared Sidecar
Each service gets its own isolated cloudflared container.

Describe alternatives you've considered

The current workaround is manually deploying cloudflared as a separate
Docker service and configuring Traefik + DNS by hand, as documented in
Dokploy's own guide. This works but requires significant manual effort
and leaves room for misconfiguration (SSL loops, 502 errors, mixed
content issues — as seen in linked issues).

Additional context

Working implementation available at https://github.com/bkbalci/dokploy/tree/feature/cloudflare-tunnel, happy to open a draft PR.

Domain popup:

Domain status (shared connector) :

Domain status (sidecar) :

Cloudflare settings page :

Cloudflare settings page shared connectors :

Will you send a PR to implement it?

Yes

Start by reviewing the feature/cloudflare-tunnel branch and Dokploy's existing Cloudflare guide, then trace the Cloudflare API, Traefik, and Docker service entry points involved. Done means a documented, tested integration supporting existing tunnels, a Dokploy-managed shared connector, and per-service cloudflared sidecars without the listed routing or SSL issues.