Merge main hotfixes into dev for 1.1.0 release (#522)

* Remove 'anonymous' terminology from UI copy

- Update Quickname detail copy from 'You always start anonymous' to 'You control how you show up'
- Simplify join event message to always say 'You joined as [Name]' instead of 'You joined anonymously as [Name]'

* Bump build number to 2 for 1.0.6 hotfix resubmission

* Raise FD soft limit to 512 for users with many conversations

The default iOS soft limit of 256 file descriptors is insufficient for
users with ~50 conversations, as each XMTP conversation requires
database connections and sockets. Raises the soft limit to 512 at app
launch before any XMTP clients are created.

Also bumps build number to 3 for hotfix resubmission.

* Bump version to 1.0.7 (build 1)

The 1.0.6 train is closed on App Store Connect. Bumps marketing version
to 1.0.7 and resets build number to 1 for the hotfix submission.

* Cap pending invite inboxes, expire stale ones, and add debug view

- Add maxAwakePendingInvites (default 3) to limit how many pending
  invite XMTP clients are active simultaneously. Previously, all
  pending invite inboxes were force-woken on app launch regardless
  of the maxAwakeInboxes limit, which could result in 50+ active
  clients for users who scanned many invite codes without approval.

- Detect stale pending invites older than 7 days on app launch.
  Automatic deletion is temporarily disabled — stale invites are
  logged but not removed, pending validation via the debug view.

- Only consider invites with <= 1 conversation member as deletable.
  Invites where the user has actually been added to the group (more
  than 1 member) are never deleted, preventing accidental data loss.
  Additionally, inboxes with any other conversations are preserved.

- Update sleep() to allow sleeping over-cap pending invite inboxes
  while still protecting inboxes under the cap.

- Update attemptWake() to enforce the pending invite cap when both
  the pending cap and overall capacity are exceeded.

- Add PendingInviteDebugView accessible from Settings (temporarily
  visible in production) showing all pending invites with creation
  date, wait duration, member count, and client/inbox IDs. Expired
  invites (> 7 days) are highlighted in a separate section with a
  hold-to-delete button that fully cleans up the inbox record,
  keychain identity, and lifecycle manager tracking.

- Inbox and keychain deletion failures are caught individually so
  one failure does not prevent cleanup of remaining invites.

- Add PendingInviteDetail model (with memberCount) and repository
  methods for the debug view and stale invite queries.

- Add 17 new tests: 6 for pending invite cap behavior, 4 for stale
  expiry detection, and 7 for deleteExpiredPendingInvites covering
  basic deletion, multi-member protection, other-conversations
  protection, recent invite preservation, lifecycle manager cleanup,
  partial failure resilience, and empty state.

* Remove duplicate cleanupStalePendingInvites() call

* Fix broken string interpolation in log message

* Remove accidentally committed sqlite files

---------

Co-authored-by: Quarter <1807900+onefovrth@users.noreply.github.com>

Author: yewreeka

ConvosCore/Tests/ConvosCoreTests/DeleteExpiredPendingInvitesTests.swift

@@ -203,16 +203,16 @@ struct DeleteExpiredPendingInvitesTests {
     func testSkipsRecentInvites() async throws {
         let dbManager = MockDatabaseManager.makeTestDatabase()
         let identityStore = MockKeychainIdentityStore()
-        let oneHourAgo = Date().addingTimeInterval(-1 * 60 * 60)
+        let twoHoursAgo = Date().addingTimeInterval(-2 * 60 * 60)
 
         try await insertInboxAndIdentity(
             dbManager: dbManager, identityStore: identityStore,
-            inboxId: "inbox-1", clientId: "client-1", createdAt: oneHourAgo
+            inboxId: "inbox-1", clientId: "client-1", createdAt: twoHoursAgo
         )
         try await dbManager.dbWriter.write { db in
             try makeDBConversation(
                 id: "draft-recent", inboxId: "inbox-1", clientId: "client-1",
-                inviteTag: "tag-1", createdAt: oneHourAgo
+                inviteTag: "tag-1", createdAt: twoHoursAgo
             ).insert(db)
         }