chore-cleanup-translations

[EdLeckert]

Cleanup of translations and minor adjustments. Looks worse than it is because strings.json was overwritten (and can be ignored).

1. While I couldn't find a definitive reference in the "official" docs, the consensus seems to be that strings.json should be exactly the same as the primary language in the translations folder, en.json. This is probably for backward compatibility, and the duplicate hopefully can eventually go away. Have copied en.json to strings.json.
2. Error strings do not get translated in non-core integrations. Converted them to the text in core: homeassistant/strings.json
3. Slightly out of scope, but errors for badly formatted URLs during config flow were falling thru to the generic Exception and getting displayed as "Unexpected exception". Now trap the aiohttp InvalidURL exception and display message showing example formatting.

Here's the existing behavior for a "cannot_connect" error, as in wrong IP address:

New behavior:

Also for invalid url formatting:

Finally, invalid authentication:

Let me know what you think.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[vinteo]

I was hoping they would "fix" the error code translation in non core but its been years and they haven't done it so I guess we just have to copy it which is a shame.