Call to solver : trial for simplification

[guilpier-code]

This PR follows PR #2450 (that removes direct call to Sirius and forces Sirius behind ortools).
This is a trial for simplifications of code calling the optimization weekly solver call (mainly in opt_appel_solveur_lineaire.cpp)

What was done :

• Correlate solver destruction (delete) with setting solver to null
  (to keep in mind : deleting a nullptr is harmless)
• what else ?

To be done :

• in ORTOOLS_Simplexe(...), instead of updating Probleme->ExistenceDUneSolution and use it in , we could use solver (type MPSolver) returned status.

CAUTION :

Remove changes on CI yaml files !

[a-zakir]

• Correlate solver destruction (delete) with setting solver to null
  (to keep in mind : deleting a nullptr is harmless)

  • what else ?

i'd say building unique_ptr from MPSolverFactory so we don't have to call ORTOOLS_LibererProbleme.
if resource release is important you could use std::unique_ptr<T,Deleter>::release

[guilpier-code]

We used to test ExistenceDUneSolution != SPX_ERREUR_INTERNE.
But ExistenceDUneSolution == SPX_ERREUR_INTERNE is impossible : indeed, ExistenceDUneSolution is given by ortools now, which does not know value SPX_ERREUR_INTERNE.

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
84.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud