Add link to integration docs from service control

[spacegaier]

Breaking change

Proposed change

Adds a help icon with a link tot he integration documentation for the selected service domain.

UI mode:

YAML mode:

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 Add URL Link to Documentation in the Service Call Tools [/developer-tools/service]  #8278
• 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

[spacegaier]

@bramkragten Is this PR something that you think makes sense? If yes, I will resolve the merge conflicts, otherwise of course not 😄.

[bramkragten]

With the new UI I don't think it is really useful anymore? The docs will be based on the same data as we show in the UI in the future.

[spacegaier]

With the new UI I don't think it is really useful anymore? The docs will be based on the same data as we show in the UI in the future.

In the docs there can be more than just the service data, such as additional context info, examples, etc. Even though that is then not strictly tied to the service testing, it might make it easy to navigate to look up some additional details.

[bramkragten]

I'll ask advise from our docs maistro, @frenck

Personally I don't really see the use...

[SeanPM5]

I could see this being useful in certain scenarios. An example would be a TTS service that supports multiple voices/languages, the available voices are usually listed in the docs.

[frenck]

Got pinged by @spacegaier on this matter...
I don't have an opinion on this matter.

I hope we can generate documentation for services based on the service descriptions (so in the end, it should be the same). 🤷