If bleak is running in a .app (e.g. created with py2app), then scanning
in macOS 12 works as it did in previous versions, so we don't need to
log the error. We can determine this by checking the bundle id since
Python itself is a .app and has a bundle id.

Related: #720

bytearray(val) will create a zero-filled instance of length val.
bytearray([val]) will create a bytearray containing val.

bluezdbus: Return the battery percentage in an array

Skip logging CoreBlueooth scanner error if running as .app

Apple has fixed the bug in macOS that caused Bleak to be treated as
a background app and not return scan results unless a service UUID
was provided.

black finally has a stable release, so we shouldn't expect breaking changes for a year

Black is stable now, so we shouldn't have to do this again for a whole year.

Local device info object for pair/unpair

* Add a Multiple Device Troubleshooting Sections

- Add information / tips to help with:
  - Connection issues to multiple devices
  - Pass more parameters to notify callback function

Fixes #754

This fixes a leak of the future passed to _disconnect_futures in
CentralManagerDelegate.disconnect(). As with other methods, this future
is only valid for the duration of the method call.

This was probably just a typo since _disconnect_callbacks also starts
with _disconnect.

This removes the disconnect callback from self._disconnect_callbacks
when a device disconnects. This ensures that the callback is not called
more than once and that objects referenced by the callback are not leaked
if the remote device initiates the disconnection and the disconnect method
is never called.

This documents a couple of common macOS issues.

Fixes #768

corebluetooth: suppress error message in macOS 12.3

docs/troubleshooting: common macOS issues

…ered the filters to match the bluez documentation.

…filters-bluez

Adds filters Discoverable and Pattern to the Bluezdbus scanner.

Mac fixes