chore: fix unit test

[wesk]

Problem

Unit test started failing after #672 was merged, which adds an assert about the config space for the MOREA method. The unit test was returning an invalid config space, which failed the assert.

Solution

Have the mock blackbox return a specific config space.

Alternative considered: we can actually remove the mock_blackbox entirely, but then the test would run for >1sec.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

Patch coverage: 62.50% and project coverage change: +0.09 🎉

Comparison is base (5440b05) 65.83% compared to head (be4b101) 65.92%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #678      +/-   ##
==========================================
+ Coverage   65.83%   65.92%   +0.09%     
==========================================
  Files         397      398       +1     
  Lines       27767    27782      +15     
==========================================
+ Hits        18280    18315      +35     
+ Misses       9487     9467      -20     

Impacted Files	Coverage Δ
syne_tune/config_space.py	84.54% <ø> (ø)
...izer/schedulers/searchers/regularized_evolution.py	71.83% <25.00%> (-0.23%)	⬇️
...chmarking/benchmark_commons/test_hpo_main_local.py	100.00% <100.00%> (ø)
tst/schedulers/test_rea.py	100.00% <100.00%> (ø)

... and 3 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[mseeger]

Let us at least use the correct space for these benchmarks:

    hp_cols = ["hp_x0", "hp_x1", "hp_x2", "hp_x3", "hp_x4", "hp_x5"]

    config_space = {
        node: choice(
            ["avg_pool_3x3", "nor_conv_3x3", "skip_connect", "nor_conv_1x1", "none"]
        )
        for node in hp_cols
    }
    config_space["epochs"] = 200

[wesk]

Updated