Automatically determine the advertising interval for bluetooth devices

[bdraco]

Proposed change

Currently we rely on the bluetooth stack to tell us when a device is no longer available. That makes sense for connectable devices, but for devices that do not require an active connection they can sleep for a long time, wake up, broadcast, and go back to sleep to save battery.

To solve this we now collect the maximum time between 16 advertisements and only declare these devices unavailable once we see it miss advertising. If we can't automatically determine the advertising interval we will use the 15m fallback interval currently used for scanners that do not have their own tracking stack (esphome).

This also allows us to have a better metric to determine when advertisements are stale and we should switch adapters when there are multiple adapters for both connectable and non-connectable devices.

fixes #78702
fixes #79178
fixes #78195
fixes #78380
fixes #78261

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.

[homeassistant]

Hey there @OttoWinter, @jesserockz, mind taking a look at this pull request as it has been labeled with an integration (esphome) you are listed as a code owner for? Thanks!

[bdraco]

We should do this for active devices as well, but not for unavailability, just to know when to switch to another adapter on failure

[bdraco]

Testing

• fail over
• performance
• unavailability

[bdraco]

Turned out to be smaller than expected. It took a lot more testing time than actual time writing code (but doesn't everything)

[bdraco]

Need to adjust the tests and I think this should be GTG if I don't find anything when adjusting the tests