Removed a couple of print statments I shouldn't have put in.
All new OpenRocketAPI, utilizes SteppingEventSimulationEngine instead of
UserControlledSimulation
New SteppingEventSimulationEngine almost working.
SteppingEventSimulationEngine: New class which fully mimics the behavior
of the non-stepping SimulationEngine used in RunSimulation.
OpenRocketAPI: Many changes to reflect use of the new
SteppingEventSimulationEngine.
FlightDataStep: reformated documentation, 
FlightDataType: moved TYPE_TIME_STEP to the top of the list for easier
access
OpenRocketAPI SimulationRun (without stepping, as openrocket would
normally run) and SimulationStep (with stepping enabled) should provided
matching outcomes, are both deterministic, and the FlightData object is
populated correctly when running in stepping mode so that data can be
retrieved after the simulation is complete as well.

OpenRocketAPI is using a new class extended the BasicSimulationEngine
called SteppingSimulationEngine. I've tried to make it as minimal and
easily understandble mutation of the BasicSimulationEngine. 

FullCSVOut function is new, and allows rockettalk just to ask for a full
csv including all data at the end of a simulation.