DB: Separate tables for CollabTopicLocalAccept and CollabTopicRemoteAccept

Previously there was just CollabTopicAccept, which worked only for local topics
but pretended to apply to both, due to directly pointing to Collab, thus
possible to insert rows even if there's a CollabTopicRemote.

The new situation is a new CollabTopicLocal table to which the local topic
things point, thus keeping the local and remote data separate and difficult to
confuse.

th/models

@@ -595,30 +595,35 @@ Collab
 --
 --    UniqueCollabRoleLocal collab
 
-CollabTopicLocalRepo
+CollabTopicLocal
     collab CollabId
+
+    UniqueCollabTopicLocal collab
+
+CollabTopicLocalRepo
+    collab CollabTopicLocalId
     repo   RepoId
 
     UniqueCollabTopicLocalRepo collab
 
 CollabTopicLocalDeck
-    collab CollabId
+    collab CollabTopicLocalId
     deck   DeckId
 
     UniqueCollabTopicLocalDeck collab
 
 CollabTopicLocalLoom
-    collab CollabId
+    collab CollabTopicLocalId
     loom   LoomId
 
     UniqueCollabTopicLocalLoom collab
 
-CollabTopicAccept
-    collab CollabId
+CollabTopicLocalAccept
+    collab CollabTopicLocalId
     accept OutboxItemId
 
-    UniqueCollabTopicAcceptCollab collab
-    UniqueCollabTopicAcceptAccept accept
+    UniqueCollabTopicLocalAcceptCollab collab
+    UniqueCollabTopicLocalAcceptAccept accept
 
 CollabTopicRemote
     collab CollabId
@@ -628,6 +633,13 @@ CollabTopicRemote
 
     UniqueCollabTopicRemote collab
 
+CollabTopicRemoteAccept
+    collab CollabTopicRemoteId
+    accept RemoteActivityId
+
+    UniqueCollabTopicRemoteAcceptCollab collab
+    UniqueCollabTopicRemoteAcceptAccept accept
+
 -------------------------------- Collab sender -------------------------------
 
 CollabSenderLocal