Clean up stale ZHA database listener when reconnecting to radio

[puddly]

Proposed change

A stale database listener is left over if the initial radio connection fails and ZHA performs one of its internal retries to try again. This PR incorporates a bumped version of the zigpy package (0.58.0) that includes a fix. This PR also corrects an issue with config entry unload and HA Core shutdown closing the ZHA gateway.

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 ZHA not starting after 2023.10 update #101836, fixes Discarding _save_attribute event - Slow Zigbee responses, database issue? #101288
• 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
• I have followed the perfect PR recommendations
• 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.

[home-assistant]

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

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign zha Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[frenck]

Removed it from the patch milestone, as it has quite a big conflict.

Upcoming Wednesday the beta starts for the next release, so I suggest to just await that.

[puddly]

@frenck Is there anything I can do to make it easier to merge?

This PR fixes a problem with ZHA startup that prevents radios from functioning if they require a second connection attempt to get working. If there's another PR that conflicts with this one, perhaps we can drop that one instead?