bluez.Manager: Do not handle Battery1 when removing objects

We do need to send a battery-created signal when blueman is dealing with
existing batteries. But in my testing we always see an interface-removed
signal from BlueZ. Fixes #3233

Author: infirit

blueman/bluez/Manager.py

@@ -60,7 +60,6 @@ def _on_object_added(self, _object_manager: Gio.DBusObjectManager, dbus_object:
     def _on_object_removed(self, _object_manager: Gio.DBusObjectManager, dbus_object: Gio.DBusObject) -> None:
         device_proxy = dbus_object.get_interface('org.bluez.Device1')
         adapter_proxy = dbus_object.get_interface('org.bluez.Adapter1')
-        battery_proxy = dbus_object.get_interface('org.bluez.Battery1')
 
         if adapter_proxy:
             assert isinstance(adapter_proxy, Gio.DBusProxy)
@@ -72,11 +71,6 @@ def _on_object_removed(self, _object_manager: Gio.DBusObjectManager, dbus_object
             object_path = device_proxy.get_object_path()
             logging.debug(object_path)
             self.emit('device-removed', object_path)
-        if battery_proxy:
-            assert isinstance(device_proxy, Gio.DBusProxy)
-            object_path = device_proxy.get_object_path()
-            logging.debug(object_path)
-            self.emit('battery-removed', object_path)
 
     def _on_interface_added(self, _object_manager: Gio.DBusObjectManager, dbus_object: Gio.DBusObject,
                             _dbus_interface: Gio.DBusInterface) -> None: