Rename available_bounds to inclusion_bounds in PowerManager Reports

They are still the available inclusion limits based on the actor's
priority, but the new (old) name makes it easier to contrast with
exclusion bounds, which will be introduced in the next commits.

Signed-off-by: Sahas Subramanian <[email protected]>

Author: shsms

src/frequenz/sdk/actor/_power_managing/_base_classes.py

@@ -58,8 +58,8 @@ class Report:
     target_power: Power
     """The currently set power for the batteries."""
 
-    available_bounds: Bounds
-    """The available bounds for the batteries, for the actor's priority.
+    inclusion_bounds: Bounds
+    """The available inclusion bounds for the batteries, for the actor's priority.
 
     These bounds are adjusted to any restrictions placed by actors with higher
     priorities.

src/frequenz/sdk/actor/_power_managing/_matryoshka.py

@@ -176,5 +176,5 @@ def get_status(
 
         return Report(
             target_power=self._target_power.get(battery_ids, Power.zero()),
-            available_bounds=Bounds(lower=lower_bound, upper=upper_bound),
+            inclusion_bounds=Bounds(lower=lower_bound, upper=upper_bound),
         )

tests/actor/_power_managing/test_matryoshka.py

@@ -55,8 +55,8 @@ def test_bounds(
     ) -> None:
         report = algorithm.get_status(batteries, priority, system_bounds)
         assert report.target_power.as_watts() == expected_power
-        assert report.available_bounds.lower.as_watts() == expected_bounds[0]
-        assert report.available_bounds.upper.as_watts() == expected_bounds[1]
+        assert report.inclusion_bounds.lower.as_watts() == expected_bounds[0]
+        assert report.inclusion_bounds.upper.as_watts() == expected_bounds[1]
 
     test_tgt_power(priority=2, power=25.0, bounds=(25.0, 50.0), expected=25.0)
     test_bounds(priority=2, expected_power=25.0, expected_bounds=(-200.0, 200.0))

tests/timeseries/_battery_pool/test_battery_pool_control_methods.py

@@ -141,7 +141,7 @@ def _make_report(
     ) -> _power_managing.Report:
         return _power_managing.Report(
             target_power=Power.from_watts(power),
-            available_bounds=_power_managing.Bounds(
+            inclusion_bounds=_power_managing.Bounds(
                 lower=Power.from_watts(lower),
                 upper=Power.from_watts(upper),
             ),