Ignore existing fixme pylint warnings in tests (#119500)

Co-authored-by: Robert Resch <robert@resch.dev>

tests/components/emulated_hue/test_hue_api.py

@@ -1651,6 +1651,7 @@ async def test_only_change_contrast(hass: HomeAssistant, hass_hue, hue_client) -
     )
 
     # Check that only setting the contrast will also turn on the light.
+    # pylint: disable-next=fixme
     # TODO: It should be noted that a real Hue hub will not allow to change the brightness if the underlying entity is off.
     # giving the error: [{"error":{"type":201,"address":"/lights/20/state/bri","description":"parameter, bri, is not modifiable. Device is set to off."}}]
     # emulated_hue however will always turn on the light.
@@ -1664,6 +1665,7 @@ async def test_only_change_hue_or_saturation(
 ) -> None:
     """Test setting either the hue or the saturation but not both."""
 
+    # pylint: disable-next=fixme
     # TODO: The handling of this appears wrong, as setting only one will set the other to 0.
     # The return values also appear wrong.
 

tests/components/energy/test_sensor.py

@@ -87,6 +87,7 @@ async def test_cost_sensor_no_states(
         "data": energy_data,
     }
     await setup_integration(hass)
+    # pylint: disable-next=fixme
     # TODO: No states, should the cost entity refuse to setup?
 
 

tests/components/zha/test_climate.py

@@ -1458,6 +1458,7 @@ async def test_set_moes_operation_mode(
     [
         (0, PRESET_AWAY),
         (1, PRESET_SCHEDULE),
+        # pylint: disable-next=fixme
         # (2, PRESET_NONE),  # TODO: why does this not work?
         (4, PRESET_ECO),
         (5, PRESET_BOOST),

tests/components/zha/test_light.py

@@ -454,6 +454,7 @@ async def test_light_initialization(
 
     assert entity_id is not None
 
+    # pylint: disable-next=fixme
     # TODO ensure hue and saturation are properly set on startup