Feature/817 mechanism for zeroing effector control alg msg outputs

[Natsoulas]

• Tickets addressed: issue No easy mechanism for zeroing effector control algorithm message outputs #817
• Review: By commit
• Merge strategy: Merge (no squash)

Description

This PR addresses the issue of FSW algorithm modules failing to zero their output messages when disabled, which could lead to runaway operations. The approach taken was to review effector interface modules and implement consistent zeroing functionality in their reset methods.

The following modules were modified to zero their output messages in their Reset methods:

• rwMotorVoltage
• torque2Dipole
• dipoleMapping
• forceTorqueThrForceMapping
• torqueScheduler
• thrusterPlatformReference
• thrusterPlatformState

Each implementation follows the same pattern:

1. Create a zeroed message payload using the appropriate _zeroMsgPayload() function
2. Write this zeroed message to the output message structure

Some modules like thrustRWDesat were found to already have the necessary zeroing functionality in place.

Verification

The changes were validated by:

1. Reviewing each module's code structure to ensure the zeroing functionality was implemented correctly
2. added unit tests to existing test files for each module to cover the new reset feature
3. Ensuring consistency in the implementation approach across all modules
4. Verifying that the zeroing occurs in the Reset method, which is called when modules are disabled
5. Ensuring all existing unit tests still pass

No new tests were added as this is a safety enhancement to existing functionality. The existing module tests will continue to validate the behavior of these modules.

Documentation

The release notes have been updated to include an entry about this enhancement.
The .rst documentation for all relevant effectors have been updated to mention the zeroing behavior on reset.
No other documentation was invalidated by these changes as they merely enhance existing functionality.

Future work

No immediate future work is anticipated. However, as new effector interface modules are added to the codebase, they should follow this pattern of zeroing output messages in their reset methods to maintain consistent safety behavior.

[schaubh]

Getting close, need to address a few small items. Shouldn't take long.

[schaubh]

Almost there. Some simple RST formatting fix, and updating the unit tests to check, after the simulation runs, that calling Reset() does zero the module effector output messages. Then we are building this functionality into our unit tests.

[schaubh]

good to go.