ci(sonarqube): add non-blocking SonarQube analysis on push to main

Mirrors the website repo's setup: a source-based scan of app/src/main
(Kotlin) that reports to the self-hosted SonarQube server after merge,
never gating PRs. Project key runic-gateway-android-app.

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

.gitea/workflows/sonarqube.yml

@@ -8,7 +8,7 @@
 # Prerequisites (one-time, in the Gitea UI — Repo → Settings → Actions):
 #   • Secret   SONAR_TOKEN     — a SonarQube "Analysis" token generated at
 #                                My Account → Security in SonarQube for the
-#                                Runic-Gateway-Android-app project (or a global one).
+#                                runic-gateway-android-app project (or a global one).
 #   • Variable SONAR_HOST_URL  — the SonarQube base URL on your LAN, e.g.
 #                                http://192.168.0.56:9000
 #     (kept as a variable, not committed, so the internal address stays out of git.)

sonar-project.properties

@@ -1,9 +1,9 @@
 # SonarQube analysis config for the Android-app repo.
 # Consumed by the scanner in .gitea/workflows/sonarqube.yml on push to main.
 # The project key must match the one created in SonarQube (dashboard URL
-# ?id=Runic-Gateway-Android-app).
+# ?id=runic-gateway-android-app).
 
-sonar.projectKey=Runic-Gateway-Android-app
+sonar.projectKey=runic-gateway-android-app
 sonar.projectName=runic gateway android app
 
 # Analysed application code. The single :app module's Kotlin sources.