(v3.5.2) SB3 Logger bug fix with wandb

[AlejandroCN7]

Description

Fixes a minor issue with the SB3 logger to record data in the same location as the WandB session for our environments.

Motivation and Context

In algorithms like PPO, there is no problem since the step counter aligns with those of the environment. However, in other algorithms like SAC, some synchronization mismatches can occur between the algorithm's steps and the actual steps taken in the environment, which caused the data not to be logged in the latter case.

This PR fixes the issue by ensuring that logs to WandB made from the native SB3 logger do not cause an increment in the number of steps, and therefore in the X-axis of the graphs.

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

Fixes #(issue or issues)

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:

• Scripts: Train updated with traceback show (useful for wandb).
• LoggerEvalCallback: Updated eval freq to avoid empty episodes in any environment.
• Logger: Native SB3 logger updated for no specify step in wandb log.