fix: use named parameters in wear DeviceRegistration calls

The positional args broke when pushUrl/pushEncrypt were added to
DeviceRegistration. Boolean was being passed where String? was
expected. Named parameters make this resilient to parameter order.

Author: sk7n4k3d

wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/integration/MobileAppIntegrationPresenterImpl.kt

@@ -31,10 +31,10 @@ class MobileAppIntegrationPresenterImpl @Inject constructor(
 
     private suspend fun createRegistration(deviceName: String): DeviceRegistration {
         return DeviceRegistration(
-            appVersionProvider(),
-            deviceName,
-            messagingTokenProvider(),
-            false,
+            appVersion = appVersionProvider(),
+            deviceName = deviceName,
+            pushToken = messagingTokenProvider(),
+            pushWebsocket = false,
         )
     }
 

wear/src/main/kotlin/io/homeassistant/companion/android/phone/PhoneSettingsListener.kt

@@ -210,10 +210,10 @@ class PhoneSettingsListener :
             serverId = serverManager.addServer(temporaryServer)
             serverManager.integrationRepository(serverId).registerDevice(
                 DeviceRegistration(
-                    appVersionProvider(),
-                    deviceName,
-                    messagingTokenProvider(),
-                    false,
+                    appVersion = appVersionProvider(),
+                    deviceName = deviceName,
+                    pushToken = messagingTokenProvider(),
+                    pushWebsocket = false,
                 ),
             )
             launch {