Add notification permission bottom sheet

[TimoPtr]

Summary

In the new onboarding the notification permission is displayed when we reach the dashboard instead of having a dedicated screen.

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.

Screenshots

Any other notes

This PR is based on #6081

[jpelgrom]

Happy flow functionally works OK, even though I personally preferred the placement in the onboarding flow.

[Copilot]

Pull request overview

This PR adds a notification permission bottom sheet that appears in the WebView screen after the dashboard loads, replacing the previous dedicated permission screen in the onboarding flow. The implementation uses the Home Assistant design system components and stores the user's permission preference to avoid repeated prompts.

Key Changes

• Added preference storage for tracking whether to ask for notification permission
• Implemented a modal bottom sheet UI component requesting notification permission
• Integrated the permission request into the WebView screen after initialization

Reviewed changes

Copilot reviewed 8 out of 9 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
common/src/main/res/values/strings.xml	Added localized strings for notification permission dialog title, content, and button labels
common/src/main/kotlin/io/homeassistant/companion/android/common/data/prefs/PrefsRepository.kt	Added interface methods for managing notification permission preference
common/src/main/kotlin/io/homeassistant/companion/android/common/data/prefs/PrefsRepositoryImpl.kt	Implemented preference storage methods with default value of true
app/src/main/kotlin/io/homeassistant/companion/android/webview/WebViewPresenter.kt	Added presenter interface methods to expose permission preference logic
app/src/main/kotlin/io/homeassistant/companion/android/webview/WebViewPresenterImpl.kt	Implemented presenter methods delegating to PrefsRepository
app/src/main/kotlin/io/homeassistant/companion/android/webview/WebViewContentScreen.kt	Added NotificationPermission composable with bottom sheet UI and integrated into main screen
app/src/main/kotlin/io/homeassistant/companion/android/webview/WebViewActivity.kt	Added state management and callback handling for permission request flow
app/src/screenshotTest/kotlin/io/homeassistant/companion/android/webview/WebViewContentScreenScreenshotTest.kt	Updated screenshot tests with new parameters and added test case for permission request

[github-actions]

Test Results

 87 files  ±0   87 suites  ±0   6m 52s ⏱️ -35s
784 tests +4  784 ✅ +4  0 💤 ±0  0 ❌ ±0 
797 runs  +4  797 ✅ +4  0 💤 ±0  0 ❌ ±0 

Results for commit c05dfb3. ± Comparison against base commit 5e0098b.

♻️ This comment has been updated with latest results.

[jpelgrom]

Code looks good and function works as expected. I'm interested in the background behind design but that's not a blocker for merging.

[TimoPtr]

@jpelgrom I've added this since I'm removing it from the Settings in #6115

[jpelgrom]

The setting should be added for each new server though when using minimal, while this pop-up is only shown once if the permission is missing (so probably the first server added).

[TimoPtr]

That's where having it in the onboarding was easier :/. Should we in minimal always show the sheet ?

[jpelgrom]

Yes I would always show it for minimal, because it's setting up a persistent connection which may not be necessary for each server but drain some battery.