refactor: remove GitLab CI config and docs after full Gitea migration

- Delete .gitlab-ci.yml (replaced by .gitea/workflows/ci.yml)
- Delete docs/deployment/gitlab.md (superseded by gitea.md)
- Update audit rules to reference .gitea/workflows/*.yml
- Update validate_audit.py to check Gitea CI paths
- Clean up GitLab references in gitea.md, mkdocs.yml, .dockerignore
- Mark IPv6 AAAA records as completed in hetzner docs

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

docs/deployment/gitea.md

@@ -1,6 +1,6 @@
 # Gitea CI/CD Deployment Guide
 
-This document describes how to **self-host Gitea** on an external server and migrate CI/CD from GitLab to **Gitea Actions** (GitHub Actions-compatible).
+This document describes how to **self-host Gitea** on an external server with **Gitea Actions** CI/CD (GitHub Actions-compatible).
 
 ---
 
@@ -8,8 +8,8 @@ This document describes how to **self-host Gitea** on an external server and mig
 
 - Lightweight, self-hosted Git forge (single binary or Docker image)
 - Built-in CI/CD via **Gitea Actions** (GitHub Actions-compatible YAML)
-- Built-in migration tool imports repos, issues, and PRs from GitLab
-- Low resource usage compared to GitLab
+- Built-in migration tool imports repos, issues, and PRs from other forges
+- Low resource usage
 
 ---
 
@@ -176,22 +176,15 @@ git push gitea --tags
 ### Option B: Gitea built-in migration (code + issues + PRs)
 
 1. In Gitea, click **+** > **New Migration**.
-2. Select **GitLab** as the source.
-3. Enter your GitLab URL and a Personal Access Token.
-4. Gitea will import the repository, issues, labels, milestones, and merge requests.
+2. Select the source forge (GitHub, GitLab, etc.).
+3. Enter the source URL and a Personal Access Token.
+4. Gitea will import the repository, issues, labels, milestones, and pull/merge requests.
 
 ---
 
-## 6. CI/CD — GitLab vs Gitea Actions
+## 6. CI/CD — Gitea Actions
 
-The workflow file lives in `.gitea/workflows/ci.yml` (already created in this repository).
-
-| GitLab CI (`.gitlab-ci.yml`) | Gitea Actions (`.gitea/workflows/ci.yml`) |
-|------------------------------|-------------------------------------------|
-| `stages:` + `stage:` per job | Jobs run in parallel; use `needs:` for ordering |
-| `services:` (top-level on job) | `services:` nested under each job with `options:` |
-| `allow_failure: true` | `continue-on-error: true` |
-| `rules: - if:` | `on:` triggers + `if:` conditionals per job |
+The workflow file lives in `.gitea/workflows/ci.yml` (already created in this repository). Gitea Actions uses GitHub Actions-compatible YAML syntax.
 | `artifacts: paths:` | `actions/upload-artifact@v4` (not supported on Gitea GHES) |
 | `cache: paths:` | `actions/cache@v4` |
 | `coverage: '/regex/'` | Use coverage action or parse in step |
@@ -299,14 +292,3 @@ docker run --rm -v gitea-data:/data -v $(pwd):/backup alpine \
 ```
 
 ---
-
-## 12. Removing GitLab (After Migration)
-
-Once you have verified everything works on Gitea:
-
-1. Update your local git remote:
-    ```bash
-    git remote set-url origin ssh://git@git.yourdomain.com:2222/your-username/letzshop-product-import.git
-    ```
-2. The `.gitlab-ci.yml` file can be removed from the repository.
-3. Archive or delete the GitLab project.