Rework CloudhookURL setup for mobile app

[TimoPtr]

Proposed change

This PR attempts to make sure that whenever the CloudhookURL is sent to the mobile_app, the mobile_app can use it. Today the issue we have is that even when the CloudhookURL is deleted it stays in the Entry. Because of that the mobile_app continue to try to use it, causing a failure and the app to fallback to external/internal URLs.
The app cannot assume that the CloudhookURL has been removed since it might be a temporary failure, it needs to come from core that has the knowledge.

The chosen approach is to register a listener on the cloud that is triggered when the CloudhookURL is deleted so that we can remove it from the Entry too.

The CloudhookURL was also sent when the subscription was not active which makes no sense for the mobile_app because the CloudhookURL is not usable in this state.

In order to react to the disable/enable of a CloudHook I've decided to change how we set the CloudHookURL by using a listener instead of using the value created, otherwise we cannot determine when the Cloudhook is enabled back without reloading the mobile_app integration.

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

Combining with home-assistant/android#6072 this should remove most of the error going to HA Cloud and reduce drastically the load. Since today all the users that have canceled their subscription are still making requests to HA Cloud even if they all fail. This changes is important for HA Cloud but also for our users by reducing useless queries.

Checklist

• I understand the code I am submitting and can explain how it works.
• 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 Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/cloud, mind taking a look at this pull request as it has been labeled with an integration (cloud) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of cloud 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 cloud Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (mobile_app) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of mobile_app 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 mobile_app Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[edenhaus]

Thanks @TimoPtr 👍

[edenhaus]

The tests are failing please have a look at it

Comment addressed