Feature/74 petting zoo

[Mark2000]

Description

Closes #74
Closes #97

Refactors reward to be on a per-sat basis.
Implements the PettingZoo parallel api for MARL.

How should this pull request be reviewed?

• By commit
• All changes at once

Type of change

• 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 not work as expected)

How Has This Been Tested?

One integrated test is flakey because of #59 , which allows the satellite to become a zombie.

• Unit tests (General Environment only) pytest --cov bsk_rl/envs/general_satellite_tasking --cov-report term-missing tests/unittest
• 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.1b0
• Platform: MacOS

Checklist:

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