Add multiengine capability to 2DOF missions

[jkirk5]

Summary

Added multiengine capability to 2dof mission analysis. The throttle allocator was added for phases that actually used throttle as a control (basically just cruise), while the other phases had throttle shape set to be able to accept multiple throttles per node. Nothing was changed about how throttle was used for each phase, so they are still mostly user-set static values per-phase.

I think there is potential to consolidate the existing add_throttle_control in 2dof ODEs with the updated add_subsystems_and_solver present in all ODES (from BaseODE class).

Related Issues

• Resolves #

Backwards incompatibilities

None

AI Usage

AI was used to:

• debug some issues with why throttle indices were mismatched, helping to trace where their values ultimately get set from for the different 2dof phases.
• Re-work function on line 105 in mission/utils.py to support 2d throttle vectors
• Re-work epsilon function in compute of PercentNotInFuselage component of geometry/gasp_based/engine.py to support multiengine

[jkirk5]

The 2DOF throttle allocation test always returns a 50/50 split between the engines which definitely seems wrong, and I will need to dig in a little more to verify it is actually working