Refactor/v1 0 0

[Mark2000]

Description

Closes #115 Closes #82 Closes #80 Closes #70 Closes #55 Closes #19 Closes #17 Closes #16 Closes #14 Closes #11 Closes #10 Closes #9 Closes #8

In progress.

Type of change

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

How should this pull request be reviewed?

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

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Passes 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
• [x] Examples (General Environment only) pytest tests/examples

Test Configuration

• Python:
• Basilisk:
• Platform:

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
• [ ] 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

[Mark2000]

Will squash changes later, anticipating adding more PRs on review.

[Mark2000]

Also looking for opinions on what to do with the deprecated folder.

[Mark2000]

Note to self: Update pages build pipeline, remove version warning on index.rst, and release notes date just before merging.

[LorenzzoQM]

About the deprecated folder, I don't think we need to keep it in this release, especially considering that some of the code in there might require some changes to work with the updated repo.