docs(web): fold the stale profile-setting comments into one

Renaming the component left three consecutive doc blocks above it, two of them
describing controls that no longer exist separately.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: juliusmarminge

apps/web/src/components/settings/IntegrationsSettings.tsx

@@ -504,28 +504,21 @@ function DesktopOnlyBrowserDefaults({ children }: { readonly children: ReactNode
   );
 }
 
-/**
- * Create, rename, and remove browser profiles.
- *
- * Built-ins render without controls: they are synthesized rather than stored,
- * so there is nothing to rename and removing them would strand every tab that
- * opened under them.
- */
-
-/**
- * Per-profile cookie import from a browser installed on this machine.
- *
- * Sources are listed lazily on open: detection touches the other browser's
- * files, and the answer changes while the app is running (quitting the browser
- * clears `browserRunning`), so a value cached at mount would go stale.
- */
 /**
  * Profile list, its header menu, and the import flow.
  *
  * One menu creates profiles and imports into them, because the two are the
  * same decision from the user's side: "I want a profile that has my Helium
  * logins in it". Import targets include "New profile" so that case does not
  * require creating one first and then finding a second control.
+ *
+ * Built-ins render without a rename field: they are synthesized rather than
+ * stored, so there is nothing to rename and removing them would strand every
+ * tab that opened under them.
+ *
+ * Sources are listed lazily on open: detection touches the other browser's
+ * files, and the answer changes while the app is running (quitting the browser
+ * clears `browserRunning`), so a value cached at mount would go stale.
  */
 function BrowserProfilesSetting({ disabled }: { readonly disabled: boolean }) {
   const userProfiles = useClientSettings((settings) => settings.browserProfiles);