refactoring: VectoRuns now use background worker, driving cycle has progress indicator, vectorun updates progress

- distinguish between current driving behavior for estimating next simulation interval in case the vehicle accelerates
- new testcase for accelerating during coasting before brake (due to slope change)

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

modified testcase for distance test: distanceBasedDrivingCycle now drives across slope changes (only speed changes are met exactly)

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)

Merge branch 'feature/VECTO-124-pdf-report' of https://webgate.ec.europa.eu/CITnet/stash/scm/~emkrispmi/vecto-sim into feature/VECTO-125-comparison-of-vecto2.2-and-vecto3