Issue #106: Implement logging module

[Mark2000]

Description

Closes #106

Implements the python logging module. @LorenzzoQM would be interested to hear your opinions about if we should log less/more and what logging levels are appropriate. There's a lot that could be done here, like coloring logs, etc. but this feels like a good minimal product.

How should this pull request be reviewed?

• [ ] By commit
• [X] All changes at once

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Updated tests.

• [X] Unit tests (General Environment only) pytest --cov bsk_rl/envs/general_satellite_tasking --cov-report term-missing tests/unittest
• [X] Integrated tests (General Environment only) pytest --cov bsk_rl/envs/general_satellite_tasking --cov-report term-missing tests/integration

Test Configuration

• Python: 3.10.11
  • Basilisk: 2.2.2
• Platform: MacOS

Checklist:

• [X] My code follows the style guidelines of this project (passes Black, ruff, and isort)
• [X] I have performed a self-review of my code
• [X] I have commented my code, particularly in hard-to-understand areas
• [X] I have made corresponding changes to the documentation
• [X] Commit messages are atomic, are in the form Issue #XXX: Message and have a useful message
• [X] My changes generate no new warnings
• [X] I have added tests that prove my fix is effective or that my feature works
• [X] New and existing unit tests pass locally with my changes

[Mark2000]

Pushed fixes that should eliminate erroneous logging. Also fixed the logger when multiple environments are instantiated, sequentially, could still be a problem in parallel applications, like training. Will read up on logging filters and think about it more.