Shutdown coordinator on entry unload

[epenet]

Proposed change

Linked to #91360
Based on feedback from @frenck in #91744

Replaces:

• Fix lingering timers in asuswrt #91457
• Fix lingering timer in rainmachine #91724
• Fix lingering timer in prusalink #91726
• Fix lingering timer in shelly #91729
• Fix lingering timer in wled #91744

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
• 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.

[epenet]

Should it shutdown on all coordinators that have a config entry?
Or should we add a specific argument?

Suggested change

	if self.config_entry:
	self.config_entry.async_on_unload(self.async_shutdown)
	if shutdown_on_entry_unload:
	assert self.config_entry
	self.config_entry.async_on_unload(self.async_shutdown)

[bdraco]

I’m struggling to think of a case where you wouldn’t want to shutdown on unload. I think it would be a bug to not.

[epenet]

CI failure is due to wallbox tests leaking into one-another (fixed in #91752)

[frenck]

That is not exactly what I meant with my comment (my comment was intended to move the shutdown internally inside the WLED to a different location).

But nevertheless, this solution works as well and improves the "just works" experience.

Thanks, @epenet 👍

../Frenck