(v3.0.6) - Sinergym Callbacks fix in SB3 evaluation and logs

[AlejandroCN7]

Description

This minor update try to improve the Sinergym callbacks for SB3 evaluations and logs. Logging is now more flexible and uniform. Sinergym was sensitive to the class of SB3 algorithm used for the record of the metrics. With this patch, Sinergym can fix the dump frequency of the data and not depend on the algorithm type (On or Off Policy basically).

Motivation and Context

• I have raised an issue to propose this change (required for new features and bug fixes)

Why is this change required? What problem does it solve? Please, reference issue or issues opened previously.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (update in the documentation)
• Improvement (of an existing feature)
• Others

Checklist:

• I've read the CONTRIBUTION guide (required)
• My change requires a change to the documentation.
• I have updated the tests.
• I have updated the documentation accordingly.
• I have reformatted the code using autopep8 second level aggressive.
• I have reformatted the code using isort.
• I have ensured cd docs && make spelling && make html pass (required if documentation has been updated.)
• I have ensured pytest tests/ -vv pass. (required).
• I have ensured pytype -d import-error sinergym/ pass. (required)

Changelog:

• Improved LoggerCallback, new argument called dump_frequency added, and it is uniform for all algorithms.
• Fixed comfort violation condition during training.
• Improved some Sinergym logger names (in SB3 algorithms and its local logger).
• Added new metrics in evaluation logs.
• Improved code for loggers.
• Fixed some attributes get with new gymnasium protocol (v3.0.5)
• Updated env attribute name experiment_path to workspace_path.
• Updated documentation and tests.
• Updated notebooks outputs