Show per-container resource usage in monitoring

What problem will this feature address?

When self-hosted users open the Monitoring page, they can see server-level usage but cannot quickly identify which running Docker container is currently responsible for CPU, memory, disk I/O, or network I/O usage. Troubleshooting requires leaving Dokploy and running Docker commands manually on the server.

Describe the solution you'd like

Add a Resource Usage breakdown to the Monitoring page that lists running containers with current CPU, memory, disk size, disk I/O, and network I/O usage. Users should also be able to expand a container row to inspect its top processes by CPU and memory usage.

A PR is already open for this implementation: #4571

Describe alternatives you've considered

The current workaround is to use Docker CLI commands such as docker stats, docker top, and manual inspection outside Dokploy. That works, but it is slower and less discoverable for users who are already monitoring their server from Dokploy.

Additional context

The proposed PR keeps this scoped to the self-hosted Dokploy container monitoring view, reuses the existing monitoring permission model, validates Docker container IDs before process inspection, and includes tests plus a screenshot.

Will you send a PR to implement it?

Yes

Review PR #4571 first, since it contains the implementation for this feature. Compare its monitoring-page changes with the stated requirements for container CPU, memory, disk, and network usage, expandable top processes, permission reuse, Docker ID validation, tests, and the screenshot.