Rename the Gitea repo references to ProLibertateGames

The repo was renamed from PilgrimsOfKatan to ProLibertateGames on the
Gitea instance. Update every reference so nothing points at the old name:

- OTA updater: the repo constant and the User-Agent
- publish-release.sh: the default repo, the asset name, the release title
- CI/release workflows: the artifact names and the staged APK name
- settings.gradle.kts: the Gradle project name
- Protocol.kt / LanTransport.kt: the mDNS service label and the Wi-Fi lock tag
- docs (README, CLAUDE.md, docs/CI.md) and the update-policy test fixtures

The installed applicationId is left unchanged in this commit.

Co-Authored-By: Paperclip <[email protected]>

docs/CI.md

@@ -1,11 +1,11 @@
 # CI, releases, and OTA — decisions and how to build
 
-Status as of the Pilgrims of Katan bootstrap (WALA-118).
+Status as of the ProLibertateGames bootstrap (WALA-118).
 
 ## Decisions
 
 1. **The release channel is this instance's own releases.** The app ships from
-   <https://git.wallacenet.ca/devadmin/PilgrimsOfKatan>, and the in-app updater
+   <https://git.wallacenet.ca/devadmin/ProLibertateGames>, and the in-app updater
    reads that repo's releases over Gitea's REST API. GitHub is not a channel for
    this project; the only GitHub URLs left are the `upstream` remote and the
    attribution link in the README.
@@ -113,8 +113,8 @@ so a retry is safe.
 
 | Channel | Endpoint |
 | --- | --- |
-| production | `GET /api/v1/repos/devadmin/PilgrimsOfKatan/releases/latest` |
-| dev | `GET /api/v1/repos/devadmin/PilgrimsOfKatan/releases?limit=30` |
+| production | `GET /api/v1/repos/devadmin/ProLibertateGames/releases/latest` |
+| dev | `GET /api/v1/repos/devadmin/ProLibertateGames/releases?limit=30` |
 
 - `/releases/latest` is documented by Gitea as *the most recent non-prerelease,
   non-draft release* — the same rule GitHub implements, so the production
@@ -126,7 +126,7 @@ so a retry is safe.
   `prerelease`, `draft`, and assets carrying `browser_download_url`. Gitea says
   `limit` where GitHub says `per_page`.
 - Each asset must be named so it contains its tag —
-  `PilgrimsOfKatan-v1.4.1001.apk` for tag `v1.4.1001` — because the updater
+  `ProLibertateGames-v1.4.1001.apk` for tag `v1.4.1001` — because the updater
   picks the versioned APK out of the release's assets by that rule.
 
 `BuildConfig.OTA_ENABLED` is a kill switch, not a channel decision: it is