Fault injection classes

[pranavnarayan26]

This pull request creates individual fault injection classes for reaction wheel, coarse sun sensor, and thruster faults. Each class is implemented as a Basilisk module, and can therefore be automated within simulation as any other Basilisk module.

The reaction wheel faults are similar to loss of effectiveness: either max torque is decreased, or increased friction is introduced. The coarse sun sensor faults utilize the built in fault statuses in Basilisk - several stuck points, turning completely off, or random spikes. The thruster faults are relatively simple - at random times, the a thruster turns on at max thrust for a very short interval.

In addition, simple one-dimensional scenarios are created to test and demonstrate each of these faults; the detection of these faults is also considered in testing scripts for LIME and SHAP on Random Forest.

Note: the commits, since many of them were made before my last pull request, are still messy. I apologize for that; the last three commits should be slightly better.

[MartinAstro]

Not going to nitpick right now, but in general the commits are too long and should be more atomic. If your creating a script, the break your commits down into the respective sections of that script. If you are adding new funcitonality, then add the functionality in one commit, and deploy it in a seperate commit, etc. In current form, it's had to inspect all of the things that changed and decide if the changes are what the commit message says they are.

Approving for now just to get it in, but moving forward I recommend adopting a more granular, atomic commit style. Good first go at it though.