Introduce observe entity for display

[TimoPtr]

Summary

In the automotive screen we are going to need to be able to have updates of the entity that we are going to be display. This PR add the obverse capability to the GetEntityForDisplayUseCase so that a consumer can get the entity updates from the WebSocket when available. I replace the invoke operator with a snapshot method.

I tested the observe method by simply replacing the snapshot per a observe in the ManageTileViewModel and the entities were properly updating within the UI when the state was changing.

Checklist

• New or updated tests have been added to cover the changes following the testing guidelines.
• The code follows the project's code style and best_practices.
• The changes have been thoroughly tested, and edge cases have been considered.
• Changes are backward compatible whenever feasible. Any breaking changes are documented in the changelog for users and/or in the code for developers depending on the relevance.

Any other notes

I'm not sure if we should use observe instead of snapshot in the EntityPicker. @jpelgrom wdyt?

[Copilot]

Pull request overview

This PR updates the GetEntitiesForDisplayUseCase API to support continuous updates via a new observe(...) Flow (driven by entity state changes and registry update events) while replacing the previous invoke operator usage with explicit snapshot(...) methods for one-time resolution.

Changes:

• Added GetEntitiesForDisplayUseCase.observe(...) to emit updated EntityDisplayState.Loaded snapshots when entity states/registries change, and renamed the old entry points to snapshot(...).
• Refactored display resolution so EntityDisplayItem can be constructed from an Entity to resolve state-derived fields once (state, raw state, active/executing, coordinates, alarm metadata).
• Updated callers and tests to use snapshot(...), and added comprehensive Turbine-based tests covering observe behavior.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/display/GetEntitiesForDisplayUseCase.kt	Introduces observe(...), refactors registry snapshot fetching, and renames one-shot API to snapshot(...).
common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/display/EntityDisplayItem.kt	Expands EntityDisplayItem to include entity-derived display fields and adds a constructor that resolves them from an Entity.
common/src/test/kotlin/io/homeassistant/companion/android/common/data/integration/display/GetEntitiesForDisplayUseCaseTest.kt	Updates snapshot tests and adds a new nested test suite validating observe(...) update behavior.
app/src/test/kotlin/io/homeassistant/companion/android/settings/qs/ManageTilesViewModelTest.kt	Updates mocks to the new snapshot(...) API.
app/src/main/kotlin/io/homeassistant/companion/android/widgets/todo/TodoWidgetConfigureViewModel.kt	Switches to getEntitiesForDisplay.snapshot(...).
app/src/main/kotlin/io/homeassistant/companion/android/util/compose/entity/EntityPicker.kt	Uses the EntityDisplayItem(Entity) constructor for metadata-free display mapping.
app/src/main/kotlin/io/homeassistant/companion/android/settings/vehicle/ManageAndroidAutoViewModel.kt	Switches to getEntitiesForDisplay.snapshot(...).
app/src/main/kotlin/io/homeassistant/companion/android/settings/shortcuts/legacy/ManageShortcutsViewModel.kt	Switches to getEntitiesForDisplay.snapshot(...).
app/src/main/kotlin/io/homeassistant/companion/android/settings/qs/ManageTilesViewModel.kt	Switches to getEntitiesForDisplay.snapshot(...).
app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearFavoritesView.kt	Replaces EntityDisplayItem.from(entity) with the new constructor.

[TimoPtr]

@jpelgrom I was going to introduce a sealed class on top of the EntityDisplayItem but I'm not sure at the moment and went with the null approach and kept a generic entity.

[github-actions]

Test Results

  276 files    278 suites   19m 34s ⏱️
2 433 tests 2 430 ✅ 2 💤 1 ❌
2 465 runs  2 462 ✅ 2 💤 1 ❌

For more details on these failures, see this check.

Results for commit 7c91332.

♻️ This comment has been updated with latest results.

[jpelgrom]

I'm not sure if we should use observe instead of snapshot in the EntityPicker. @jpelgrom wdyt?

I think we shouldn't use observe unless there is a need to keep things live, to limit data use and recompositions - a picker that just loaded should be fine with snapshot, not expecting it to go out of date.

[TimoPtr]

I'm not sure if we should use observe instead of snapshot in the EntityPicker. @jpelgrom wdyt?

I think we shouldn't use observe unless there is a need to keep things live, to limit data use and recompositions - a picker that just loaded should be fine with snapshot, not expecting it to go out of date.

That's the direction I've followed in this PR but I wanted your opinion. It's nice to see the list updating but I think probably overkill.