Adds workflow to publish nvitop-exporter

[ntheanh201]

• Creates a new GitHub Actions workflow to automatically build and publish the nvitop-exporter Docker image to GitHub Container Registry (GHCR) on releases.

Issue Type

• Improvement/feature implementation

Runtime Environment

• Operating system and version: [e.g. Ubuntu 20.04 LTS / Windows 10 Build 19043.1110]
• Terminal emulator and version: [e.g. GNOME Terminal 3.36.2 / Windows Terminal 1.8.1521.0]
• Python version: [e.g. 3.8.2 / 3.9.6]
• NVML version (driver version): [e.g. 460.84]
• nvitop version or commit: [e.g. 0.10.0 / 0.10.1.dev7+ga083321 / main@75ae3c]
• python-ml-py version: [e.g. 11.450.51]
• Locale: [e.g. C / C.UTF-8 / en_US.UTF-8]

Description

Motivation and Context

Testing

Images / Videos

[XuehaiPan]

Hi @ntheanh201, thanks a lot for the contribution!

This PR looks good. But before merging this, I am wondering whether it is worth having a separate docker image for nvitop-exporter. It is very easy to install with pipx or uvx. For docker users, they can access nvitop-exporter via the docker image for uv (uvx).

docker run -it --rm --runtime=nvidia --gpus=all \
    ghcr.io/astral-sh/uv:python3.13-bookworm-slim \
    uvx nvitop-exporter

[ntheanh201]

Hi @XuehaiPan, you're right about your concern. But I still think it's better when everyone gets a ready-to-run container instead of having to remember the uvx command (in the scope of my PR)