feat: add container resource breakdown to monitoring

[agentHits]

What is this PR about?

This PR adds a self-hosted Resource Usage breakdown to the Monitoring page. It shows the current CPU, memory, disk size, disk I/O, and network I/O usage per running Docker container, and lets users expand a container row to inspect its top processes by CPU/memory usage.

The feature is only exposed for the Dokploy container monitoring view and reuses the existing monitoring:read permission. Docker container IDs are validated before running docker top, and the Cloud version keeps the same restricted behavior as the existing monitoring endpoints.

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 in your local instance. If you have not tested it yet, please do so before submitting. This helps avoid wasting maintainers' time reviewing code that has not been verified by you.

Testing

• corepack pnpm --dir apps/dokploy exec vitest --config __test__/vitest.config.ts __test__/monitoring/container-resource-usage.test.ts --run
• corepack pnpm exec biome check apps/dokploy/__test__/monitoring/container-resource-usage.test.ts apps/dokploy/components/dashboard/monitoring/container-resource-usage/container-resource-usage.tsx apps/dokploy/components/dashboard/monitoring/container-resource-usage/utils.ts apps/dokploy/components/dashboard/monitoring/free/container/show-free-container-monitoring.tsx apps/dokploy/server/api/routers/server.ts packages/server/src/services/docker.ts
• corepack pnpm --filter=dokploy run typecheck
• corepack pnpm --filter=server run typecheck
• corepack pnpm --filter=dokploy run build-server
• corepack pnpm --filter=dokploy run build-next
• corepack pnpm --filter=server run build
• Tested locally at http://localhost:3000/dashboard/monitoring with the Resource Usage table expanded and container process drill-down verified.

Issues related (if applicable)

Closes #4653

Screenshots (if applicable)

[agentHits]

I need all this because I can’t figure out which container or which service is causing such heavy loads that my VPS is freezing. Therefore, I would like to see this moment, if I have any such loads and loads, I would like to receive a notification in Telegram that a certain container is starting to heavily load my VPS, that it stops responding to me.

[agentHits]

Rebased on latest canary (439f57566) and re-verified locally after rebase.

Checks run:

• corepack pnpm install --frozen-lockfile
• corepack pnpm --filter=dokploy exec vitest run --config __test__/vitest.config.ts __test__/monitoring/container-resource-usage.test.ts
• corepack pnpm exec biome check apps/dokploy/__test__/monitoring/container-resource-usage.test.ts apps/dokploy/components/dashboard/monitoring/container-resource-usage/container-resource-usage.tsx apps/dokploy/components/dashboard/monitoring/container-resource-usage/utils.ts apps/dokploy/components/dashboard/monitoring/free/container/show-free-container-monitoring.tsx apps/dokploy/server/api/routers/server.ts packages/server/src/services/docker.ts
• corepack pnpm --filter=dokploy run typecheck
• corepack pnpm --filter @dokploy/server run typecheck

CI may remain in action_required until GitHub Actions is approved for this fork PR.

[agentHits]

@Siumauricio this PR now has a linked feature request (#4653), was rebased on the latest canary, and was re-verified locally after rebase. Could you please review it when you have time and approve the GitHub Actions workflow run for this fork PR?

[luanupe]

Any updates? I'm really looking forward to this change.

[agentHits]

Any updates? I'm really looking forward to this change.
@luanupe
Bro, there's only one admin here and this repo has a ton of vulnerabilities. I'm currently fixing them in my fork, and I'll also add all the functionality that was suggested here. The admin is silent and barely crawling like a turtle. I consider myself doing work and want to rely on my own development because the admin doesn't devote enough time to this project. Apparently, he's only concerned about money and earning money from people, and he's not interested in security or improving the project - because I don't see a reason why he hasn't confirmed all my PRs yet.

Join me in co-developing and forking https://github.com/agentHits/dokploy/tree/AgentHits-Dev

This is so you understand what kind of work I'm doing on dokploy