Use new localized context state and source in logbook

[bdraco]

Does not need to wait for home-assistant/core#72333 since we can't rewrite history. (the source was only exposed on the original message and missing from the context message).

Proposed change

• Refactor to remove more static english strings that come from the backend

• Everything should be localized except for external events (https://github.com/home-assistant/frontend/pull/12742/files#diff-fe0260e1d2f2eea8dcb455d644828da865c94f2522881f2abd0a24012f808cc0R413)

Fixes #12698 (except for the backend messages that come from integrations since we don't control thoose)

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 #
• 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

[bdraco]

I moved localizeTriggerSource next to localizeStateMessage in data/logbook since it seemed like it was a better fit there.

[kukulich]

I've really tried to understand the PR and I'm not sure if it fully fixes #12698 ...

It looks much much better (eg. ui.components.logbook.for is gone) but it still looks (based on the screenshots) that texts are concatenated together... It would be still difficult for translator to translate it in a way that make sense.

Something like this can be traslated more easier:

Light turned on
Triggered by automatition: Some automatition name
Triggered by state of: Some entity

[zsarnett]

We can merge today most likely. Ill review this soon. Just need to fix the conflicts with your other PR

[bdraco]

It looks much much better (eg. ui.components.logbook.for is gone) but it still looks (based on the screenshots) that texts are concatenated together... It would be still difficult for translator to translate it in a way that make sense.

Something like this can be traslated more easier:

Light turned on
Triggered by automatition: Some automatition name
Triggered by state of: Some entity

Unfortunately, while it is easier to translate, splitting makes it look inconstant which means it would need a UX redesign which is outside the scope of this PR.

Since this is an improvement over the last iteration, and it will make it easier to refactor into a multi-line setup later. I suggest we merge this now and iterate on the UX design in the future.

[kukulich]

Since this is an improvement over the last iteration, and it will make it easier to refactor into a multi-line setup later. I suggest we merge this now and iterate on the UX design in the future.

I totally agree 👍 It is already an improvement 👍 I just hope that the UX redesign will not be forgotten :)