refactoring default driver strategy: do not switch action due to speed changes (close before the action)

add a name attribute to the distance-run (to know which cycle/loading combination is currently running)

if search braking power finds a value <0 => overload response. driver strategy has to find another way to proceed...
(can happen if the gear is disengaged and the requested deceleration can not be reached, i.e. the deceleration is higher)

gearbox disengages when braking and engine-speed would drop below idle speed

- introduce driver info about desired behavior

- open the clutch if the vehicle's speed gets too low and the engine speed goes below idle speed

consider the case that 'nextTargetSpeed != 0' for computing the next simulation distance

make vehicle code testable, test for airdrag resistance, adapt componentdata files to new file format

Additional property in mission to disinguish which CdA Value to use (Rigid Truck, Longhaul Cycle w/ trailer)