Bump bleak to 0.19.0

[bdraco]

Proposed change

Bump bleak to 0.19.0

There are breaking changes in the library but they are not user facing. Breaking changes in the lib only affect Home Assistant development. These changes likely do not affect libraries except for the first one which has a transition time.:

• The .rssi property has moved from the BLEDevice to the AdvertisementData (its on both during transition)
• AdvertisementData no longer have defaults and must all be set (this breaks many tests)
• Relocations (needs feat: update for bleak 0.19 home-assistant-libs/home-assistant-bluetooth#9) home-assistant-libs/home-assistant-bluetooth@v1.3.0...v1.6.0
• Package updates feat: update for new bleak 19 Bluetooth-Devices/bleak-retry-connector#52 Bluetooth-Devices/bleak-retry-connector@v2.1.3...v2.2.0

In exchange for the breaking changes we avoid almost all the linear searches for BLEDevice or AdvertisementData, as well as the ability to exchange some coroutines for callback functions which allows the manager to be refactored to be much more efficient at handling unavailable devices.

Future PRs to handle the deprecation after this PR

• At least following packages will need an update as they use device.rssi but they will come in future PRs:

Sent upstream issue

• melnor - rssi has moved from BLEDevice to AdvertisementData in bleak 0.19.0+ vanstinator/melnor-bluetooth#40

Sent upstream PR

• keymitt_ble - sent PR upstream Updates for bleak 0.19.0 spycle/pyMicroBot#1

Completed or has PR

• aiohomekit - Bump aiohomekit to 2.1.0 for bleak 0.19.0 #80426 Update for bleak 0.19.0 Jc2k/aiohomekit#190
• yalexs_ble - Bump yalexs_ble to 1.9.4 for bleak 0.19.0 #80406
• led_ble Update led-ble to 1.0.0 for bleak 0.19 #80403
• airthings_ble - verified does not need to be updated
• pySwitchbot Bump pySwitchbot to 0.20.0 for bleak 0.19 changes #80389
• ibeacon_ble - validated that this uses BluetoothServiceInfo abstraction so it will already work
• fjäråskupan - Bump fjaråskupan to 2.2.0 #80401
• snooz - verified does not need to be updated
• xiaomi_ble - validated that this uses BluetoothServiceInfo abstraction so it will already work

Semi-related to this PR, but I noticed we are missing docs for

• async_last_service_info Update bluetooth documentation for bleak 0.19 changes developers.home-assistant#1497

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[bdraco]

Thanks. I'll start working on the libs.

I also found a race when there are multiple non connectable scanners and connectable scanners and the closest one to the device is non connectable. Will work on a fix for that once I get a valid test written. Doesn't look like we can fix that in a patch release but I expect I can have it worked out for 2022.11 and it's less likely to be a concern anyways now that esphome devices are connectable

[bdraco]

I also found a race when there are multiple non connectable scanners and connectable scanners and the closest one to the device is non connectable. Will work on a fix for that once I get a valid test written. Doesn't look like we can fix that in a patch release but I expect I can have it worked out for 2022.11 and it's less likely to be a concern anyways now that esphome devices are connectable

Fixed the race here #80388