fix(telegram): restore in-place editing with proper v0→v1 migration

The previous removal of migration logic left existing users stuck with
refreshInPlaceEnabled=false in stored data. Add back the migration to
restore old data (v0) to the original intended default of true,
while preserving v1+ data as-is.

Without this, users see separate messages instead of one bubble being
edited in place (5.4 → 5.3 → 5.7 should be edits, not 4 messages).

Author: Rob

Common/src/main/java/tk/glucodata/OutboundApiSettings.kt

@@ -621,7 +621,12 @@ object OutboundApiSettings {
                 refreshInPlaceEnabled = item.optBoolean(
                     "refreshInPlaceEnabled",
                     DEFAULT_REFRESH_IN_PLACE_ENABLED
-                ),
+                ).let { stored ->
+                    // v0→v1 migration: restore edit-in-place that was incorrectly forced false.
+                    // Old data should have true (the original default); only preserve stored
+                    // value for v1+ data (user's explicit choice).
+                    if (itemSettingsVersion < 1) true else stored
+                },
                 refreshWindowMinutes = item.optInt(
                     "refreshWindowMinutes",
                     DEFAULT_REFRESH_WINDOW_MINUTES