Bump bluetooth-auto-recovery to 0.5.2

[bdraco]

Proposed change

Implements the generic usb reset in user space since the kernel will take a long time to get it:
https://lore.kernel.org/netdev/20221006170915.v3.1.I46e98b47be875d0b9abff2d19417c612077d1909@changeid/T/

changelog: Bluetooth-Devices/bluetooth-auto-recovery@v0.4.0...v0.5.2

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.

[Jc2k]

Are there any permissions we need to think about for this? Do you need to be root to do the ioctl? Or just own the file paths?

[bdraco]

Are there any permissions we need to think about for this? Do you need to be root to do the ioctl? Or just own the file paths?

There are any number of potential failure cases so I used the same strategy I did for the power off/on rollout by adding exception catches and debug logging for already known failure paths and a broad exception catch and error logging for ones we don't know about yet.

As we discover what doesn't work for some users we can trap more exceptions and downgrade to debug if needed but I'm hoping not to do that because this is the last resort to get the adapter working and once we get here if we can't reset it's a cold boot to get things working again