Overrides for post-mission (and mission?) components

Desired capability or behavior.

Aviary's override capability currently only works for pre-mission. This functionality needs to be added to post-mission as well.

There is a possibility overrides are needed for mission too, as there are plenty of intermediate calculations that have variables that a user could conceivably want to override (say a skin friction coefficient in aerodynamics or some similar, intermediate, non-time-sensitive variable)

Suggested implementation.

For post-mission the code in the pre-mission group can probably be duplicated. It may even be possible to use the same class for both groups.

For mission, I am not sure how to proceed. There isn't a custom group holding the trajectory, and I am not sure if the trajectory can be extended to have the needed configure steps

Start by locating the existing pre-mission override implementation and compare it with the post-mission group. Determine whether the same approach can support post-mission overrides, then assess how mission trajectory configuration could expose overrides. Done means post-mission overrides work and the mission-scope design is resolved or explicitly bounded.