Fix screen orientation change clearing UI state

[ArnyminerZ]

Purpose

See #719

Short description

• Added a new check: SubscriptionSettingsUseCase.UiState.isInitialized. Will just check whether the "initialization values" have been set (by setInitialValues for example).
• This check is used in the LaunchedEffect block of AddSubscriptionScreen, to make sure setInitialValues is not called again when screen is recomposed (for example, when rotating the screen).
• Also removed the @Singleton annotation from SubscriptionSettingsUseCase, because otherwise it was being shared among used instances, and state was moving around between screens.

Checklist

• The PR has a proper title, description and label.
• I have self-reviewed the PR.
• I have added documentation to complex functions and functions that can be used by other modules.
• I have added reasonable tests or consciously decided to not add tests.

[Copilot]

Pull Request Overview

Fixes an issue where screen orientation changes would clear UI state by preventing re-initialization of subscription settings values when the screen is recomposed.

• Added isInitialized() check to prevent redundant initialization calls
• Removed @Singleton annotation to avoid shared state between screen instances
• Added early return in LaunchedEffect when UI state is already initialized

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
AddSubscriptionScreen.kt	Added initialization check to prevent clearing UI state on recomposition
SubscriptionSettingsUseCase.kt	Removed singleton scope and added isInitialized method

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[sunkup]

Dirty workaround, but good for now. Please merge 👍