Handle android lifecycle in kotlin couroutine

Currently, the code in the sdk which is using kotlin couroutine is not aware of android lifecycle. Therefore, some bugs could occur after an activity / fragment was paused / stopped.

We might want to review the code and see how we can fix it.

Related article:

https://developer.android.com/topic/libraries/architecture/coroutines#restart

No files, tests, or entry points are named. Review coroutine usage in the Android SDK against the linked Android lifecycle guidance, then define and verify behavior when activities or fragments are paused or stopped so lifecycle-related bugs do not occur.

Written by the indexing model from the issue text.