Update bluetooth_le_tracker to use Bleak

[bdraco]

Needs #75381

Proposed change

Update bluetooth_le_tracker to use Bleak

I wanted to keep the change as small as possible so its still a legacy tracker but using Bleak now.

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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[bdraco]

While this change will make it push since we see new devices right away we probably still need a periodic poll of async_discovered_service_info to account for devices that the bluez backend didn't send us updates for since they had no RSSI changes as the legacy trackers rely on time

[bdraco]

We need some type of common Bluetooth mock so integrations don't actually end up setting up a scanner which won't work since the CI definitely doesn't have Bluetooth

[bdraco]

Looks like this had partial test coverage before. Should add a few more when I don't have so many irons in the fire

[MartinHjelmare]

This isn't ready for merge yet, right? The Bluetooth changes is from the other branch, I think.

[bdraco]

This isn't ready for merge yet, right? The Bluetooth changes is from the other branch, I think.

Right, its got that branch merged into it and needs to be rebased so it gets separated out once the other PR is merged.