feat: Core - Sync homeserver settings

[afterburn]

Initial setup for homeserver settings syncing, lmk if you think I need to take it into a different direction @tipogi

[MiguelMedeiros]

Issues & Recommendations

🔴 Critical: Race Condition in Controller

Location: src/core/controllers/settings/settings.ts (lines 17-22)

private static async commitUpdate(): Promise<void> {
  const pubky = Core.useAuthStore.getState().selectCurrentUserPubky();
  const settings = Core.SettingsNormalizer.extractState(Core.useSettingsStore.getState());
  await Core.SettingsApplication.commitUpdate(settings, pubky);
}

If multiple settings changes happen rapidly, each call extracts state independently. Earlier in-flight requests may overwrite later local changes when they complete, causing data loss.

Suggestion: Consider debouncing or using a queue pattern:

private static pendingCommit: Promise<void> | null = null;

private static async commitUpdate(): Promise<void> {
  // Wait for any pending commit to complete before starting a new one
  if (this.pendingCommit) {
    await this.pendingCommit;
  }
  
  const pubky = Core.useAuthStore.getState().selectCurrentUserPubky();
  const settings = Core.SettingsNormalizer.extractState(Core.useSettingsStore.getState());
  
  this.pendingCommit = Core.SettingsApplication.commitUpdate(settings, pubky);
  await this.pendingCommit;
  this.pendingCommit = null;
}

---

🟡 Medium: Muted Users Syncing Creates Unnecessary Network Calls

Location: src/core/controllers/settings/settings.ts (lines 87-104)

The muted array is explicitly not synced (normalizer always returns empty array from homeserver). However, the controller has methods like addMutedUser, removeMutedUser, setMutedUsers, clearMutedUsers that all call commitUpdate().

This triggers homeserver sync for changes that won't actually persist remotely.

Suggestion: Either:

1. Remove these methods from the controller (keep only direct store access), OR
2. Add a skipSync parameter, OR
3. Include muted in the homeserver sync

---

@afterburn can you address those so we can merge this PR?

[afterburn]

@MiguelMedeiros resolved the issues you flagged