Ensure one row per recipient in getRecipientSettingsForSync().

Technically there's no unique constraint in ThreadDatabase to guarantee
only one thread per recipient. We saw a crash that indicated that one
user has two threads for the same recipient. That's not true for any of
my devices. Still, best to play it safe here while we try to figure out
why this is happening.

app/src/main/java/org/thoughtcrime/securesms/database/RecipientDatabase.java

@@ -1079,7 +1079,7 @@ private List<RecipientSettings> getRecipientSettingsForSync(@Nullable String que
                              .flatMap(Stream::of)
                              .toArray(String[]::new);
 
-    try (Cursor cursor = db.query(table, columns, query, args, null, null, null)) {
+    try (Cursor cursor = db.query(table, columns, query, args, TABLE_NAME + "." + ID, null, null)) {
       while (cursor != null && cursor.moveToNext()) {
         out.add(getRecipientSettings(context, cursor));
       }