# Description

This PR adds support for providing a custom `ProgressReporter` while
doing hyperparameter tuning with Ray Integration.

Without the PR, the Ray integration defaults to the standard
`CLIReporter`, which often displays metrics that aren’t particularly
relevant or at the desired frequency. Similar to how we allow users to
specify a --cfg_class (e.g., `CartpoleTheiaJobCfg`), this PR lets them
optionally provide a custom `ProgressReporter` class. If such is not
provided, it falls back to the default.

Moreover, I have added an example inside `vision_cartpole_cfg.py` (i.e.,
`CustomCartpoleProgressReporter`).

One point to highlight is that the new "[context-aware progress
reporting](https://github.com/ray-project/ray/issues/36949)" conflicts
with custom `ProgressReporter`, so if a custom `ProgressReporter` is
provided, the PR disables the context-aware progress reporting.

Fixes #3268.

## Type of change

- New feature (non-breaking change which adds functionality)

## Checklist

- [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with
`./isaaclab.sh --format`
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have updated the changelog and the corresponding version in the
extension's `config/extension.toml` file
- [x] I have added my name to the `CONTRIBUTORS.md` or my name already
exists there

---------
Co-authored-by: garylvov <67614381+garylvov@users.noreply.github.com>