Use LaunchActivity in HaControlsPanel

[TimoPtr]

Summary

In order to be able to use the FrontendScreen in the lock screen when using a dashboard has ControlPanel we need the LaunchActivity to set the setShowWhenLocked flag. Today it is behind the WIPFeature.

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.

[Copilot]

Pull request overview

This PR enables LaunchActivity to optionally render over the lock screen (via setShowWhenLocked) so the device controls panel can launch the new Compose-based frontend (FrontendScreen) while the device is locked.

Changes:

• Add an optional showWhenLocked parameter to LaunchActivity.newInstance() and apply it during onCreate
• Update HaControlsPanelActivity to launch LaunchActivity (with deep link + showWhenLocked = true) when WIPFeature.USE_FRONTEND_V2 is enabled
• Add Robolectric tests covering the new showWhenLocked behavior in LaunchActivity

Reviewed changes

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

File	Description
app/src/main/kotlin/io/homeassistant/companion/android/launch/LaunchActivity.kt	Introduces showWhenLocked intent extra handling for lock-screen display
app/src/main/kotlin/io/homeassistant/companion/android/controls/HaControlsPanelActivity.kt	Switches controls panel launch target to LaunchActivity for Frontend v2 and enables lock-screen display
app/src/test/kotlin/io/homeassistant/companion/android/launch/LaunchActivityTest.kt	Adds tests validating showWhenLocked behavior

[TimoPtr]

@jpelgrom what do you think?

[TimoPtr]

I've applied the logic and used an alias and check the component name within the Intent. I hope it's enough.

[jpelgrom]

You could theoretically limit it even more to when the user's device controls preference is set to dashboard, as that is the only scenario in which we apply this flag. Your current implementation is easier to reuse though, also fine by me and seems good enough.

[TimoPtr]

Let's keep it like this for now 👍🏻

[jpelgrom]

Nice implementation and improvement.

I added two comments as replies on the Copilot comments. I guess it boils down to whether we want the extra to be generic, or scoped to the device controls usage, as for whether or not to address them. In my opinion it's fine to merge it as it currently is.