create issue breakdown: Ascent/Entry

[mdbernard]

See RPOD for reference in #16

Define these points in a comment in this issue:

• Define Take-Over points (where does the team take control of the vehicle?)
• Define Hand-Over points (where does the team stop controlling the vehicle?)
• Define Event Sequences (describe, in a sentence, what the team does with the vehicle)

Create an issue...

• for each Event Sequence to create fine-grained procedures in the form of a markdown file
• to determine algorithm similarity between Event Sequences (i.e. where could code be reused?) (determine algorithm similarity for code reuse across Ascent/Entry Event Sequences #35)
• to program each general algorithm/function to be used across multiple Event Sequences (program general-use utility functions for Ascent/Entry #36)
• to program a controlling function for each Event Sequence (controlling function for each Ascent/Entry Event Sequence #28)
• to program a Continuous Integration test for each Event Sequence's controlling function (program CI tests for all Ascent/Entry Event Sequences #37)
• to program unit tests for each function used throughout all of the team's Event Sequence scripts (except the controlling functions) (program unit tests for Ascent/Entry functions #38)

[mdbernard]

The mission's commanding script will begin with pre-launch preparation and then hand off control to A/E while SLS is on the launchpad, no stages activated.

TO1: SLS is on the launchpad.
ES1: SLS flies to Kerbin orbit.
HO1

Other teams handle trans-lunar injection, lunar landing, lunar ascent, trans-Kerbin injection.

TO2: Orion SM is still attached, 100 km above Kerbin's surface, returning from Mun.
ES2: Separate from SM and fly through atmosphere. Splashdown.
HO2