fix(wss): terminate disconnected container log streams

[gilangh]

What is this PR about?

Closes #4835.

The runtime Logs tab streams through /docker-container-logs. Previously, local streams ran docker logs --follow behind a shell/PTTY and disconnect cleanup only killed that wrapper; remote cleanup only ended the SSH client. Cleanup was also registered after asynchronous authentication/server lookup, leaving a race where a browser could disconnect before the log process was tracked.

This change:

• registers disconnect cleanup before asynchronous work starts;
• spawns the local Docker CLI directly, then escalates SIGTERM to SIGKILL after one second if needed;
• explicitly signals and closes remote SSH log channels;
• closes browser WebSockets that unmount while still connecting;
• keeps search behavior with chunk-safe, case-insensitive server-side filtering.

Checklist

Before submitting this PR, please make sure that:

• You created a dedicated branch based on the canary branch.
• You have read the suggestions in the CONTRIBUTING.md file https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#pull-request
• You have tested this PR locally.

Validation performed with Node.js 24.4.0:

• pnpm exec vitest --config __test__/vitest.config.ts __test__/wss/utils.test.ts --run (22 tests passed)
• pnpm --filter=dokploy typecheck
• pnpm --filter=@dokploy/server typecheck
• pnpm --filter=dokploy build-server
• Biome check on all changed files

Issues related (if applicable)

Closes #4835.

Screenshots (if applicable)

Not applicable; this changes server-side process lifecycle and disconnect handling.