GitHub workflows improvements

[sarahyurick]

There are a couple of GitHub Actions I want to add to NeMo Curator:

• GPU CI (already have Add GPU CI/CD #253 open for this)
• Auto label PRs with the gpuci label if the PR is (1) created by a user with write access and (2) modifying at least 1 Python file
• Automate Changelog build
• Automate PyPI releases
• Display suggested style changes when the pre-commit CI fails (e.g., with Ruff)

After the first one is merged, I can open separate PRs to add the others.

[sarahyurick]

Note from Oliver about 2:
"
This file didn’t work because using secrets.GITHUB_TOKEN is not permitted to trigger other workflows. GH disallows that to prevent spam. You would need to use your personal access token (PAT). However, since we’re in a public environment, you would need to limit that to a protected branch (via environments). It’s still doable (from branch main, react to all issue change events), but a bit more tricky. As long as the PAT is not exposed to all branches, this is fine.
"

[sarahyurick]

Additional tasks outside of GitHub:

• Set up a nightly or weekly job that runs these same PyTests with RAPIDS Nightly Builds to identify any upstream breakages (closed with Run GPU Tests on Rapids Nightly at midnight UTC #463)
• Releasebot on Slack
• CI alerts on Slack

[sarahyurick]

NeMo files of interest:

• https://github.com/NVIDIA/NeMo/blob/main/.github/workflows/_test_template.yml
• https://github.com/NVIDIA/NeMo/blob/main/.github/workflows/changelog-build.yml
• https://github.com/NVIDIA/NeMo/blob/main/.github/workflows/cherry-pick-release-commit.yml
• https://github.com/NVIDIA/NeMo/blob/main/.github/workflows/release-freeze.yml
• https://github.com/NVIDIA/NeMo/blob/main/.github/workflows/release.yml

[sarahyurick]

Suggestion from @praateekmahajan: parametrizing the GPU tests with commonly used clients.

• get_client(cluster_type="gpu", protocol="ucx")
• get_client(cluster_type="gpu", protocol="tcp")
• Maybe even set_torch_to_use_rmm/enable_spilling (we shouldn't try all the permutations, just the ones where we expect different behavior)

Depending on how many GPUs the node has we could we even try a multi-GPU setup.

[sarahyurick]

Regarding the gpuCI label:

• Always have it run (without having to re-add the label) for Nvidians/RAPIDS members
• For non-verified users we could use /okay to test comments

[sarahyurick]

Another check: unused imports.

[sarahyurick]

Another: #488.