Reimplement output constraint scaling

[verveerpj]

Issue
This PR reimplements output constraint scaling

Approach
See #9985, a similar approach for objective scaling, this PR builds on top of that.

(Screenshot of new behavior in GUI if applicable)

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure unit tests pass locally after every commit (git rebase -i main --exec 'just rapid-tests')

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Create Backport PR to latest release

[codecov-commenter]

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
437	2	435	24

View the top 2 failed tests by shortest run time

tests/everest/test_math_func.py::test_math_func_auto_scaled_constraints

Stack Traces | 0.018s run time

file .../tests/everest/test_math_func.py, line 189
  @pytest.mark.integration_test
  def test_math_func_auto_scaled_constraints(
E       fixture 'evaluator_server_config_generator' not found
>       available fixtures: _session_event_loop, anyio_backend, anyio_backend_name, anyio_backend_options, benchmark, benchmark_weave, cache, cached_example, capfd, capfdbinary, caplog, capsys, capsysbinary, change_to_tmpdir, class_mocker, control_config, control_data_no_variables, copy_egg_test_data_to_tmp, copy_math_func_test_data_to_tmp, copy_mocked_test_data_to_tmp, copy_template_test_data_to_tmp, copy_test_data_to_tmp, copy_testdata_tmpdir, cov, doctest_namespace, event_loop, event_loop_policy, filter_warnings, min_config, mock_server, mocker, module_mocker, monkeypatch, no_cover, package_mocker, pytestconfig, qapp, qapp_args, qapp_cls, qtbot, qtlog, qtmodeltester, record_property, record_testsuite_property, record_xml_attribute, recwarn, session_mocker, snapshot, testdata, testrun_uid, tests/everest/test_math_func.py::<event_loop>, tmp_path, tmp_path_factory, tmpdir, tmpdir_factory, unused_tcp_port, unused_tcp_port_factory, unused_udp_port, unused_udp_port_factory, worker_id
>       use 'pytest --fixtures [testpath]' for help on them.

.../tests/everest/test_math_func.py:189

tests/everest/test_math_func.py::test_math_func_auto_scaled_objectives

Stack Traces | 0.018s run time

file .../tests/everest/test_math_func.py, line 161
  @pytest.mark.integration_test
  def test_math_func_auto_scaled_objectives(
E       fixture 'evaluator_server_config_generator' not found
>       available fixtures: _session_event_loop, anyio_backend, anyio_backend_name, anyio_backend_options, benchmark, benchmark_weave, cache, cached_example, capfd, capfdbinary, caplog, capsys, capsysbinary, change_to_tmpdir, class_mocker, control_config, control_data_no_variables, copy_egg_test_data_to_tmp, copy_math_func_test_data_to_tmp, copy_mocked_test_data_to_tmp, copy_template_test_data_to_tmp, copy_test_data_to_tmp, copy_testdata_tmpdir, cov, doctest_namespace, event_loop, event_loop_policy, filter_warnings, min_config, mock_server, mocker, module_mocker, monkeypatch, no_cover, package_mocker, pytestconfig, qapp, qapp_args, qapp_cls, qtbot, qtlog, qtmodeltester, record_property, record_testsuite_property, record_xml_attribute, recwarn, session_mocker, snapshot, testdata, testrun_uid, tests/everest/test_math_func.py::<event_loop>, tmp_path, tmp_path_factory, tmpdir, tmpdir_factory, unused_tcp_port, unused_tcp_port_factory, unused_udp_port, unused_udp_port_factory, worker_id
>       use 'pytest --fixtures [testpath]' for help on them.

.../tests/everest/test_math_func.py:161

To view more test analytics, go to the Test Analytics Dashboard
📢 Thoughts on this report? Let us know!

[codspeed-hq]

CodSpeed Performance Report

Merging #10003 will not alter performance

_{Comparing reimplement-constraint-scaling (2bf7a0f) with main (856cc02)}

Summary

✅ 25 untouched benchmarks

[yngve-sk]

LGTM, I think this clarifies the "sampling ensemble" being there