Add support for JSON input ('BEV' only), in engineering mode, for
multiple axle powertrains. This will enable the creation of a vehicle
powertrain with multiple axle powertrains.

A tool that takes older (urn:tugraz:ivt:VectoAPI:DeclarationDefinitions
v1.0, v2.0, v2.1, v2.2.1) VECTO jobs and converts them to a newer
version (v2.4), so they can be simulated by the current version of
VECTO.

Override downshift strategy if speed reduced by half or below extended downshift polygon

See merge request vecto/vecto!230

Implement subgroup allocations for PEVs

See merge request vecto/vecto!227

HybridStrategy - modifying condition to use previous run DryRunSolution in...

See merge request vecto/vecto!229

Fix retarder loss map error in completed vehicle simulation

See merge request vecto/vecto!228

Reintroduce summary for vocationals and non vocationals cycles

See merge request vecto/vecto!225

use default values for eco roll and engine stop/start in case of HEV and PEV...

See merge request vecto/vecto!220

HybridStrategy - modifying condition to use previous run DryRunSolution in DryRun Mode + adding LimitedGbxTorque update

- added definition LimitedGbxTorque solves #462

- adding condition (DataBus.GearboxInfo.TCLocked) to use DryRunSolution
from previous run in DryRunMode solves #326, #348, #457, #458, #459,
#545 and #655 (partially)

- adding condition (!DryRunSolution.Solution.IgnoreReason.EngineSpeedBelowDownshift())
to use DryRunSolution from previous run in DryRunMode solves #346, #352,
 #394, #433, #451, #452, #453, #454 and #655 (combined with previous
condition for this last one)

In some cases, the fact of using previous run Strategy generates a
difference between operating point searched in dryRun Mode and effective
 computation (in non dryRunMode) of the acceleration found, that results
 in an overload the driver can't manage.