fix: clone the solution before sending it to the consumer

[zepfred]

This PR addresses an issue where we return the same solution instance as the SolverScope to external consumers. Therefore, if changes are made to the solution, it may be possible that these changes will affect the solver phases, because the current best solution from the solver scope is restored at the end of each phase.

AbstractSolver::runPhases(SolverScope<Solution_> solverScope) {
            ...
            // If there is a next phase, it starts from the best solution, which might differ from the working solution.
            // If there isn't, no need to planning clone the best solution to the working solution.
            if (it.hasNext()) {
                solverScope.setWorkingSolutionFromBestSolution();
            }

It is worth noting that I have analyzed the use of SolverScope::getBestSolution and external actions. The solution is now cloned before being shared with these external consumers.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[triceo]

We can still improve this a bit.