Feature/two way range check

[Mark2000]

Description

Closes #298
Closes #300

Adds enforce_range_on_chief option to MaxRangeDynModel to cause the chief to also be terminated if the deputy dies.

Also fixes an issue exposed in tests where bad behavior would happen if a satellite died at t=0.

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 should this pull request be reviewed?

• By commit
• All changes at once

How Has This Been Tested?

Updated tests.

Future Work

None.

Checklist

• I have performed a self-review of my code
• I have commented my code in hard-to-understand areas
• I have made corresponding changes to the documentation and release notes
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

[Copilot]

Pull Request Overview

This PR adds a new enforce_range_on_chief option to the MaxRangeDynModel that causes the chief satellite to also be terminated if a deputy satellite violates the maximum range constraint. Additionally, it fixes a simulation initialization issue where bad behavior occurred when a satellite died at t=0.

• Adds bidirectional range enforcement capability to MaxRangeDynModel
• Fixes simulator initialization by replacing ConfigureStopTime and ExecuteSimulation with StepUntilStop
• Updates tests to verify both chief and deputy termination behavior under range violations

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/bsk_rl/sim/dyn/relative_motion.py	Adds enforce_range_on_chief parameter and implements dynamic method binding for chief termination
src/bsk_rl/sim/simulator.py	Fixes initialization issue by changing simulation execution method
tests/integration/sim/test_int_dynamics.py	Adds parametrized tests to verify chief termination behavior
docs/source/release_notes.rst	Documents the new bidirectional range enforcement feature

Comments suppressed due to low confidence (1)

src/bsk_rl/sim/dyn/relative_motion.py:190

• The parameter name 'self' is confusing as a default argument when 'self' is already the method's first parameter. Consider renaming to 'deputy_dynamics=self' or similar to clarify this refers to the deputy's dynamics object.

            def range_valid(self, deputy=self):