Add CallbackGroup & Metadata factory function

[PytLab]

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 ?

Add global callback group & metadata factory function for NeMo

Collection: [Note which collection this PR will affect]
Will keep updating

• asr
• multimodal
• nlp

Changelog

• New CallbackGroup and Callback ABC in NeMo/nemo/lightning/pytorch/callbacks/callback_group.py

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)

To fix the issue, the unused import of CallbackGroup should be removed from the file. This will eliminate unnecessary clutter and improve code readability. The removal should be limited to the specific import statement flagged by CodeQL, ensuring no unintended changes to other parts of the code.

[dorotat-nv]

it doesnt seem to be compatible with on_validation_start of OneLoggerUtils

[dorotat-nv]

this fails if the batch specific hooks for validation are not provided

    def on_validation_batch_start(self, trainer, pl_module, batch, batch_idx, dataloader_idx=0) -> None:
        """Called when validation batch begins.

        Args:
            trainer: The PyTorch Lightning trainer
            pl_module: The PyTorch Lightning module
        """
        self.one_logger.on_validation_batch_start()

    def on_validation_batch_end(self, trainer, pl_module, outputs, batch, batch_idx, dataloader_idx=0) -> None:
        """Called when validation batch ends.

        Args:
            trainer: The PyTorch Lightning trainer
            pl_module: The PyTorch Lightning module
        """
        self.one_logger.on_validation_batch_end()

To fix the issue, the unused logging import on line 8 should be removed. This will eliminate the unnecessary dependency and make the code cleaner. No other changes are required, as the removal of this import does not affect the functionality of the code.

To fix the problem, we will remove the unused import statement from pytorch_lightning.plugins.io import AsyncCheckpointIO on line 17. This will clean up the code and eliminate the unnecessary dependency without affecting the functionality of the program.

---

[PeiyuanQi]

Eric: it is better to publish to public index, if we have difficulties, make sure this won't fail with import guard, and maybe ref to the open sourced one logger repo.

[PeiyuanQi]

Saju: we need to change this import to be the config based exporter import. so we could change the exporter destination by simple onelogger package upgrade.

To fix the issue, the unused import statement import pytorch_lightning as pl should be removed from the file. This will eliminate the unnecessary dependency and improve code clarity. No other changes are required, as the rest of the code already uses specific imports from PyTorch Lightning directly.

---

To fix the problem, the unused torch import on line 13 should be removed. This will eliminate the unnecessary dependency and make the code cleaner. No other changes are required since the removal of this import does not affect the functionality of the code.