Refactor showInAppMessage to properly handle suspend function [SC-167747]

[chrissiewasabi]

No description provided.

[Copilot]

Pull Request Overview

This PR refactors the showInAppMessage method in the Android SDK to properly handle suspend functions by using coroutines and lifecycle-aware components. The refactor addresses proper coroutine handling for asynchronous operations while adding error handling.

• Wrapped the MIClient.showInAppBrowser call in a coroutine scope to handle suspend functions properly
• Added lifecycle-aware coroutine launching using lifecycleScope
• Enhanced error handling with try-catch block and proper UI thread callback execution

Reviewed Changes

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

File	Description
package.json	Version bump from 2.1.0 to 2.1.1
RNMovableInkModule.kt	Refactored showInAppMessage to use coroutines with lifecycle scope and added error handling
build.gradle	Added androidx.lifecycle:lifecycle-runtime-ktx dependency for lifecycle-aware coroutines

---

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

[Copilot]

Missing else branch to handle the case when activity is not a LifecycleOwner. The callback should be invoked with an error message to prevent the caller from waiting indefinitely.

[Copilot]

Missing null check for currentActivity. If currentActivity is null, the callback should be invoked with an error message to handle this edge case properly.

Suggested change

	val activity = currentActivity
	val activity = currentActivity
	if (activity == null) {
	callback.invoke("Error: currentActivity is null")
	return
	}