Point docs at git.fejl40.nu after the move from GitHub

- README / CONTRIBUTING: clone from the Gitea repo.
- SECURITY: Gitea has no private security advisories; report to
  support@fejl40.nu instead.
- RELEASING: release URL on Gitea, plus a note that build.yml still uses
  the GitHub-only action-gh-release step, so no releases are produced on
  Gitea yet (server self-update via git is unaffected).

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

RELEASING.md

@@ -8,9 +8,16 @@ git commit -m "Your message"
 git push origin main
 ```
 
-GitHub Actions builds Windows and Linux binaries automatically and updates the
-**"Latest build (main)"** pre-release at:
-`https://github.com/<owner>/GDPRScanner/releases/tag/latest`
+The build workflow (`.github/workflows/build.yml`) builds Windows and Linux
+binaries and updates the **"Latest build (main)"** pre-release at:
+`https://git.fejl40.nu/Fejl40.nu/GDPRScanner/releases/tag/latest`
+
+> **Note:** the repository moved from GitHub to Gitea (`git.fejl40.nu`). The
+> workflow still publishes with the GitHub-only `softprops/action-gh-release`
+> action, so releases are **not yet produced on Gitea**. Until the workflow is
+> ported to Gitea Actions, build and attach binaries manually. Server installs
+> are unaffected — they self-update from `git.fejl40.nu` via git
+> (see `update_gdpr.sh`).
 
 ## Versioned release
 
@@ -22,7 +29,7 @@ git push origin main
 git push origin v1.6.14
 ```
 
-Actions creates a proper GitHub Release named `v1.6.14` with auto-generated
+Actions creates a proper release named `v1.6.14` with auto-generated
 release notes and the built binaries attached.
 
 Append `-beta` or `-rc` to the tag to mark it as a pre-release: