v0.4.8 — the errors speak French too

Two strings reached the user interface without passing through a translation, so a French install read them in English.

The setup failure. ConfigEntryError renders on the integration card, not just in the log, and it was built with an f-string. It now carries the corrupt_connect_export translation key.

The import rejection. Half-translated: the sentence around the reason was French while the reason injected into it was hand-written English.

A paste that is not JSON at all is now reported separately (invalid_json) from a well-formed document that is not a .connect export (invalid_connect). Their fixes differ — a truncated or word-wrapped paste versus the wrong file — and rendering them identically was the problem that message was meant to solve in the first place.

The parser's own detail stays in English on purpose: it names JSON fields that are English in the export itself.

A new test compares the key set of every shipped translation against strings.json, so a key added to one file and forgotten in another fails the suite instead of silently rendering in English for that language.

Full notes: CHANGELOG