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

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 (closed), #348 (closed), #457 (closed), #458 (closed), #459 (closed), #545 and #655 (partially)

• adding condition (!DryRunSolution.Solution.IgnoreReason.EngineSpeedBelowDownshift()) to use DryRunSolution from previous run in DryRunMode: solves #346 (closed), #352 (closed), #394 (closed), #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 gives an overload the driver can't manage.

Some additional tests have shown it also solves: #482 (closed), #514, #515 (closed), #518, #529, #544, #552, #555, #556, #557, #558, #559, #560, #622, #632, #672, #673, #674, #678, #679, #685, #686, #687, #692.