ci: Improve Run CICD experience

[ko3n1g]

Important

The Update branch button must only be pressed in very rare occassions.
An outdated branch is never blocking the merge of a PR.
Please reach out to the automation team before pressing that button.

What does this PR do ?

We have few scenarios where a PR gets updated:

• reformat code with auto-commit
• update PR button
• Modify the concurrency control so that adding more labels to the PR won't cancel the Run CICD workflow

If this happens while a Run CICD workflow is running, the check suite won't be representative anymore since the metadata is overwritten by the updated commit.
This PR adds a relabel bot that re-attaches the Run CICD label, if the label was attached prior to the update event.

Furthermore, it removes the Run CICD label after the CI has finished (success or failure, cancel will not remove it).

Considerations:

• Reformat is an action that users don't have (much) control over. So running the relabel bot after reformat makes a lot of sense to me
• Updating the PR (accidentially) is a real threat and so also re-running the CI after this seems plausible to me
• However, the re-label bot will also re-label if "normal" commits are being added. So pratically, once the Run CICD label is attached we will re-run the CI with each attached commit up until the CI finishes (success or failure). At this point the author will need to label the PR again.
• I think this is fine, since one of the events that we want to catch with this automation is the accidental "Update PR" button. From git perspective, it is difficult to distinguish between this button and a "normal" commit. So in order to have a robust mechanism, I would suggest to always restart the CI with a new commit.

Collection: [Note which collection this PR will affect]

Changelog

• Add specific line by line info of high level changes in this PR.

Usage

• You can potentially add a usage example below

# Add a code snippet demonstrating how to use this 

GitHub Actions CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you add or update any necessary documentation?
• Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

• New Feature
• Bugfix
• Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.

Additional Information

• Related to # (issue)

[jstjohn]

Yes please.

[github-actions]

[🤖]: Hi @ko3n1g 👋,

We wanted to let you know that a CICD pipeline for this PR just finished successfully

So it might be time to merge this PR or get some approvals

I'm just a bot so I'll leave it you what to do next.

//cc @pablo-garay @ko3n1g

[github-actions]

[🤖]: Hi @ko3n1g 👋,

We wanted to let you know that a CICD pipeline for this PR just finished successfully

So it might be time to merge this PR or get some approvals

I'm just a bot so I'll leave it you what to do next.

//cc @pablo-garay @ko3n1g

[ko3n1g]

Only to be merged after NeMo-FW 25.02 release to not disrupt any critical last minute operations.