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?

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)

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

[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

[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