Feature: Expose drop deployment (file upload) via public API

[fdarian]

What problem will this feature address?

Deploying to Dokploy from a CI/CD pipeline (e.g., GitHub Actions) is not possible without a git integration. I'm always frustrated when I can't do a railway up-style deployment — uploading a local build artifact (zip file) directly to Dokploy via the API. This is especially painful for monorepo setups where tools like turbo prune are used to deploy only the relevant subset of the codebase.

Describe the solution you'd like

Expose the dropDeployment endpoint in the public API so it can be called programmatically:

```
POST /api/drop-deployment
Content-Type: multipart/form-data
x-api-key:

Form fields:

• zip (required): The deployment archive (.zip)
• applicationId (required): Target application ID
• dropBuildPath (optional): Path to build configuration within the archive

Response: boolean (true on success)
```

This unlocks workflows like:

```bash
curl -X POST https:///api/drop-deployment
-H "x-api-key: "
-F "applicationId="
-F "zip=@./output.zip"
```

Describe alternatives you've considered

• Using git-based deployments — doesn't support custom build artifacts or pre-filtered content
• Self-hosting a webhook bridge — adds unnecessary infrastructure complexity
• Using the internal tRPC endpoint directly — not stable or documented for external use

Additional context

This feature depends on @dokploy/trpc-openapi supporting multipart/form-data.

Will you send a PR to implement it?

Yes

[fdarian]

@Siumauricio mind checking this? I've tested the behavior and both are working as expected. Let me know if there's any adjustments needed or if this feature isn't suitable after all.