Fix Actions discovery and Docker build: relocate workflow and custom data

- Move build-push.yml into .gitea/workflows/ so Gitea Actions actually
  discovers and triggers it (root-level workflow files are invisible to
  Gitea Actions).
- Move avast/cointelegraph/replicate/snapchat into data-custom/ so the
  Dockerfile COPY data-custom step (and build.sh) can find them instead
  of failing/silently skipping.

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

.gitea/workflows/build-push.yml

@@ -0,0 +1,29 @@
+name: Build and push geosite-build image
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch: {}
+
+jobs:
+  build:
+    # If this label isn't registered on your runner, check runner-data/.runner
+    # after registration, or set a custom label when registering act_runner.
+    runs-on: docker
+    steps:
+      # Full GitHub URL is required for actions not mirrored on your own
+      # Gitea instance — a plain "actions/checkout@v4" won't resolve.
+      - name: Checkout
+        uses: https://github.com/actions/checkout@v4
+
+      - name: Build image
+        run: |
+          docker build -t git.5838.ru/payroll3042/geosite-build:latest -f Dockerfile.scheduled .
+
+      - name: Log in to Gitea registry
+        run: |
+          echo "${{ secrets.REGISTRY_TOKEN }}" | docker login git.5838.ru -u Payroll3042 --password-stdin
+
+      - name: Push image
+        run: |
+          docker push git.5838.ru/payroll3042/geosite-build:latest