Move computing the ideal point after the optimizer has run

[odow]

We should probably time out generating primal solutions, not computing the objective bound.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.77%. Comparing base (65b565d) to head (093a0a8).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #100   +/-   ##
=======================================
  Coverage   98.77%   98.77%           
=======================================
  Files           9        9           
  Lines         980      980           
=======================================
  Hits          968      968           
  Misses         12       12           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[remi-garcia]

It would be nice if it were an option. And maybe in some cases, it could be better to not compute it at all. For instance, when we reoptimize with different weights for a Hierarchical, computing it a single time is enough.

[odow]

See https://github.com/jump-dev/MultiObjectiveAlgorithms.jl/tree/master?tab=readme-ov-file#ideal-point

set_attribute(model, MOA.ComputeIdealPoint(), false)