NelderMeadSimplex Throws Exception on Max Iterations Reached

[Quuant]

The current implementation of NelderMeadSimplex throws a MaximumIterationsException when the maximum number of iterations is reached. This add overhead, plus doesn't tell you what the latest error or simplex values were.

In many scenarios, for runtime purposes, you'd prefer to simply exit when you reach maximum iterations, rather than throw an exception.

Suggestion: It would be beneficial to return the best-found solution along with a status indicator when the maximum iterations are reached. This approach aligns with standard practices.

This can likely be applied to other optimization algorithms (haven't looked into the code extensively).