Use boundaries in optimization process for trimmer

[AlexS12]

Current situation
Right now the optimization process for trimming an aircraft does not use the control surfaces limits to constrain the results.

Objective

Tests for F16 trimming against Stevens passing without iterating out of controls surfaces ranges. Even if all the trimming validation done against Stevens for F16 converges to the same values. High Angle Of Attack (HAOA) cases require to iterate with out of range values to converge.

Avoid mutable struct for FCS As the FCS must be configured to allow out of range iteration and set back to the original values in the trimmer, it is now a mutating structure. Some other solutions to this situation may be proposed, but this would indirectly be solved if trimmer does not need out of range values.