Fix failed recovery in ipp

[ctalkington]

Breaking change

Proposed change

There have been numerous reports of IPP failing to recover from failed connection during startup to the device sleeping/shutoff and not re-establishing when it eventually wakes. This seems to have started only due to changes/optimizations to core and not to ipp integration. Roku integration also shares similar setup code and sees same behavior.

research by multiple parties seems to point to a race on unload due to the way coordinator was trying to be reused to pre-emptively avoid errors in #44413 which seems might race more often now since #91748

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 WARNING (MainThread) [homeassistant.config_entries] Config entry 'aaa.bbb.ccc.ddd' for ipp integration not ready yet: Invalid response from API: Error occurred while communicating with IPP server.; Retrying in background #93027 IPP Printer error Invalid response from API - integration not working #92714
• 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.