Merge pull request #724 in VECTO/vecto-sim from...

Merge pull request #724 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:bugfix/VECTO-789-apt-responseunderload to develop

* commit '19cf6d13':
  adding missing file
  handle null-response also in the case no max-power operating point can be found
  TC: output speed may already be too high so that no drag operating point is found (during acceleration) - use high constant value
  TC: cleaning up code, refactoring, moving some parts to separate method
  TC: in case no solution for an operating point fulfilling a certain power demand is found, and first guess is also not suitable, perform search....
  corrected error in comment
  AT gearbox: correction: requestAfterGearshift most not be set immediately but after shift losses are applied
  TC: in case the operating point for the TC is below idle speed use the same as in case no operating point is found at all
  reset braking power in case of gear switch for AT vehicles
  TC: for drag operating point search decrease engine speed to allow for negative torque (at least not keep high output power)
  Torque converter: use previous engine speed in case no operating point for certain power demand was found (more stable, reduces torque due to engien inertia)
  code formatting
  DriverStrategy BrakingMode CoastingPhase: DoCoast may return null in case a gearshift occurs - re-iterate
  in case no operating point could be found use last engine speed to avoid high inertia losses
  increase returned delta-value due to high tolerance of line search algorithm (may lead to slight over-/underload in non-dry-run request)
  Driver: in case of overload or Underload response and gear changed abort braking action
  fix for testcase: set engine inertia
  AT Gearbox: correctly handle response gearshifts from TC to consider shift losses
  extend message in case of negative brake power
  AT Shift Strategy: add shift losses for estimation of acceleration after gearshift, add engine inertia for consideration of acceleration after gearshift