fix: load data for automatic optimization (#731)

Automatic optimization used to take the adjusted load data even if there were no
measurements leading to 0 load values.

Split LoadAkkudoktor into LoadAkkudoktor and LoadAkkudoktorAdjusted. This allows
to select load data either purely from the load data database or load data additionally
adjusted by load measurements. Some value names have been adapted to denote
also the unit of a value.

For better load bug squashing the optimization solution data availability was
improved. For better data visbility prediction data can now be distinguished from
solution data in the generic optimization solution.

Some predictions that may be of interest to understand the solution were added.

Documentation was updated to resemble the addition load prediction provider and
the value name changes.

Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>

tests/test_configmigrate.py

@@ -155,7 +155,7 @@ class TestConfigMigration:
             assert configmigrate.mapped_count >= 1, f"No mapped migrations for {old_file.name}"
             assert configmigrate.auto_count >= 1, f"No automatic migrations for {old_file.name}"
 
-            assert len(configmigrate.skipped_paths) <= 7, (
+            assert len(configmigrate.skipped_paths) <= 3, (
                 f"Too many skipped paths in {old_file.name}: {configmigrate.skipped_paths}"
             )
 
@@ -174,7 +174,7 @@ class TestConfigMigration:
             errors = _dict_contains(new_data, expected_data)
             assert not errors, (
                 f"Migrated config for {old_file.name} is missing or mismatched fields:\n" +
-                "\n".join(errors)
+                "\n".join(errors) + f"\n{new_data}"
             )
 
             # --- Compare migrated result with migration map ---