Adds support for custom ProgressReporter to Ray integration

[ozhanozen]

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" 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

• I have run the pre-commit checks with ./isaaclab.sh --format
• I have made corresponding changes to the documentation
• 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
• I have added my name to the CONTRIBUTORS.md or my name already exists there

[ozhanozen]

@garylvov, would love to get your feedback if you have time!

[garylvov]

Hi thanks for the PR! (EDIT: didn't mean to mention the issue got this confused with early stopping)

[garylvov]

LGTM