[RLlib] Deprecate methods/configs for RLlib 2.0

[Rohan138]

Description

(Possible duplicate) Thought I'd open an issue to track this.

We should deprecate/remove methods like config.exploration from AlgorithmConfig and a bunch of other config options after we switch to RLModule and the other new APIs, just so we can minimize the codebase and the number of functions/APIs related to "old" RLlib that users could possibly get distracted by.

Link

E.g. #36424

[stale]

Hi, I'm a bot from the Ray team :)

To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.

If there is no further activity in the 14 days, the issue will be closed!

• If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
• If you'd like to get more attention to the issue, please tag one of Ray's contributors.

You can always ask for help on our discussion forum or Ray's public slack channel.