Refactor: Migrate from Livedata to Stateflow

[PratyushSingh07]

Summary:

StateFlow offers several advantages over LiveData. First, StateFlow promotes immutability, ensuring that its data remains unchanged once set, which enhances code reliability. Unlike LiveData, StateFlow seamlessly integrates with Kotlin's coroutines, providing powerful asynchronous programming capabilities. StateFlow handles backpressure efficiently, preventing issues related to data overflow. Additionally, StateFlow benefits from Kotlin's Flow API, offering a wide array of transformation operators for data manipulation. Lastly, StateFlow is highly testable, enabling developers to write unit tests effectively. These advantages make StateFlow a robust choice for managing and observing data streams in Android applications, especially in Kotlin-based projects.

Viewmodels that needs to be converted in this issue will be :

• LoginViewmodel
• RegistrationViewmodel
• UpdatePasswordViewmodel
• SavingAccountsDetailViewModel
• SavingAccountsTransactionViewModel
• SavingsAccountApplicationViewModel
• SavingsAccountWithdrawViewModel
• SavingsMakeTransferViewModel
• ThirdPartyTransferViewModel
• TransferProcessViewModel
• RecentTransactionViewModel
• QrCodeImportViewModel
• NotificationViewModel
• HelpViewModel
• ClientChargeViewModel
• BeneficiaryListViewModel
• BeneficiaryDetailViewModel
• BeneficiaryApplicationViewModel

It is really important that during this refactoring we dont loose our test coverage. Since the unit tests were written for livedata , the test classes will now have to be changed to support stateflows

[PratyushSingh07]

I have taken this up