Adopt blocking approach for reacting to tile events, inspired by #3974

wear/src/main/java/io/homeassistant/companion/android/tiles/TemplateTile.kt

@@ -36,6 +36,8 @@ import kotlinx.coroutines.Dispatchers
 import kotlinx.coroutines.Job
 import kotlinx.coroutines.guava.future
 import kotlinx.coroutines.launch
+import kotlinx.coroutines.runBlocking
+import kotlinx.coroutines.withContext
 import javax.inject.Inject
 import io.homeassistant.companion.android.common.R as commonR
 
@@ -94,8 +96,8 @@ class TemplateTile : TileService() {
                 .build()
         }
 
-    override fun onTileAddEvent(requestParams: EventBuilders.TileAddEvent) {
-        serviceScope.launch {
+    override fun onTileAddEvent(requestParams: EventBuilders.TileAddEvent): Unit = runBlocking {
+        withContext(Dispatchers.IO) {
             /**
              * When the app is updated from an older version (which only supported a single Template Tile),
              * and the user is adding a new Template Tile, we can't tell for sure if it's the 1st or 2nd Tile.
@@ -115,8 +117,8 @@ class TemplateTile : TileService() {
         }
     }
 
-    override fun onTileRemoveEvent(requestParams: EventBuilders.TileRemoveEvent) {
-        serviceScope.launch {
+    override fun onTileRemoveEvent(requestParams: EventBuilders.TileRemoveEvent): Unit = runBlocking {
+        withContext(Dispatchers.IO) {
             wearPrefsRepository.removeTemplateTile(requestParams.tileId)
         }
     }