Use integration manifest for service documentation URL

[spacegaier]

Breaking change

Proposed change

Use the integration manifest for the service documentation, so that it also works for custom integrations.

If the user just switches to a different service from the same domain, no re-fetching happens. Only when a different domain is used, a new fetch request is triggered.

@bramkragten Do you think we need to add static caching to only retrieve the manifest once per integration (even if in between the user selects a different domain)? I would expect that usually a user is not wildly switching around the integrations when creating e.g. automations, so there should not be that many WS calls anyway.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes Service call UI link to integration documentation is wrong for custom integrations #9919
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• 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

[bramkragten]

@bramkragten Do you think we need to add static caching to only retrieve the manifest once per integration (even if in between the user selects a different domain)? I would expect that usually a user is not wildly switching around the integrations when creating e.g. automations, so there should not be that many WS calls anyway.

Nah, don't think so