chore(config): point the updater at the now-public AeroFetch repo

The source repo is public now, so the separate releases-only repo
(AeroFetch-releases) is no longer needed to keep the updater tokenless.
Retarget UPDATE_REPO from AeroFetch-releases back to AeroFetch and refresh the
config doc comment. The dedicated read-only baked-token service account
(aerofetch-updater) has been deleted and its token revoked, so nothing reads a
token any more; the .gitignore comment for the retired .update-token file is
updated to match.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

src/main/config.ts

@@ -4,15 +4,16 @@
  * timeouts, caps, tickers) and from user settings (settings.ts). Retarget a
  * fork's update source by editing these three values.
  *
- * The update source is a PUBLIC, releases-only repo — it holds no source, just
- * the published installers — so anonymous reads work and the updater sends no
- * auth at all. Keeping releases separate from the (private) source repo is what
- * lets the client stay tokenless: there is no secret in the bundle to leak. A
- * private fork retargets its updater by editing these constants and rebuilding.
+ * The update source is the main AeroFetch repo itself, made PUBLIC — so anonymous
+ * reads work and the updater sends no auth at all; there is no secret in the bundle
+ * to leak. (A prior design split releases into a separate releases-only repo so the
+ * source could stay private; that's retired now that the source repo is public
+ * itself — one fewer moving part.) A private fork retargets its updater by editing
+ * these constants and rebuilding.
  */
 export const UPDATE_HOST = 'https://gitea.netbird.zimspace.uk:5938'
 export const UPDATE_OWNER = 'debont80'
-export const UPDATE_REPO = 'AeroFetch-releases'
+export const UPDATE_REPO = 'AeroFetch'
 export const RELEASE_API = `${UPDATE_HOST}/api/v1/repos/${UPDATE_OWNER}/${UPDATE_REPO}/releases/latest`
 
 // --- ffmpeg dependency source ------------------------------------------------